LIVE · cybersecurity feed
Live wire
finance

Third-Party JavaScript Is Part of Your Attack Surface: Lessons from a Recent Supply-Chain Attack

A recent supply-chain attack has compromised the websites of numerous high-profile organizations, including major banks, airlines, news outlets, and software firms. The incident highlights a critical vulnerability in modern web architecture: the reliance on third-party JavaScript. Rather than breaching the affected companies directly, attackers gained administrative access to a shared…

ZeroDay News ·

Source: Qualys Blog

A recent supply-chain attack has compromised the websites of numerous high-profile organizations, including major banks, airlines, news outlets, and software firms. The incident highlights a critical vulnerability in modern web architecture: the reliance on third-party JavaScript. Rather than breaching the affected companies directly, attackers gained administrative access to a shared third-party vendor platform. By compromising this vendor, the attackers were able to inject malicious code into the scripts that the vendor served to its customers.

Because the malicious code was delivered through a trusted third-party service, it bypassed traditional security measures such as server-side monitoring and internal code reviews. The compromised scripts were hosted on the vendor’s own content delivery network (CDN) and signed with valid certificates, making the malicious activity appear legitimate to both security systems and end-users. Consequently, the affected organizations unknowingly distributed the malicious payload to their own visitors.

Security researchers who analyzed the injected scripts confirmed that the code was designed to perform several malicious functions. These included the theft of payment card information entered into on-page forms, the tampering with cryptocurrency transactions, and the exfiltration of readable session cookies to servers controlled by the attackers. Because the malicious activity occurred entirely within the visitors' browsers, the affected organizations’ internal servers and source code remained untouched, rendering standard perimeter defenses ineffective.

The incident underscores the inherent risks of integrating external scripts for services like analytics, advertising, consent management, and A/B testing. Each external script effectively grants the provider the same level of privilege as the website’s own code, allowing it to manipulate page content, monitor user inputs, and access non-protected cookies. This supply-chain compromise demonstrates that a single security failure at a shared vendor can simultaneously impact a vast number of downstream customers.

While Content Security Policy (CSP) headers are intended to restrict which sources a browser can trust, the effectiveness of these policies varied significantly across the impacted sites. Many organizations lacked a robust CSP, or had configurations that were too permissive. For instance, some policies allowed the execution of malicious payloads by including directives like unsafe-eval or by failing to restrict the domains from which scripts could be loaded. Even when a vendor’s domain was allowlisted, the malicious code was able to execute because it originated from that same trusted host.

To mitigate these risks, security experts recommend that organizations maintain a comprehensive inventory of all third-party scripts, including those managed through tag managers. Reducing the number of external scripts, particularly on sensitive pages like login or payment portals, is a primary defense strategy. Furthermore, organizations are advised to implement strict CSPs that avoid unsafe directives, utilize nonces or hashes for script verification, and enable violation reporting to identify potential threats in real time.

Additional defensive measures include isolating payment entry fields within iframes served from a trusted payment provider’s domain, which prevents external scripts on the main page from accessing sensitive data. Protecting session cookies by marking them as HttpOnly, Secure, and SameSite can also prevent injected scripts from stealing authentication tokens. For scripts that do not change frequently, developers are encouraged to use Subresource Integrity (SRI) hashes or to host the files locally to ensure their integrity.

Organizations are also urged to hold their third-party vendors to higher security standards. This includes requiring multi-factor authentication or single sign-on for vendor accounts, limiting administrative access, and demanding transparency regarding how vendors secure their code-deployment pipelines. Because trusted scripts can be modified without any action from the website owner, continuous monitoring for unexpected network destinations or changes in script behavior remains a vital component of a modern security posture.

finance
ShareXLinkedInWhatsAppFacebook

More News

view all →
vulnerabilitycritical

VMware patches vCenter zero-day exploited in attacks since September

Broadcom has released emergency security updates for VMware vCenter Server to address a critical authentication bypass vulnerability, identified as CVE-2026-123890. The flaw resides within the VMware Directory Service (vmdird) and allows an unauthenticated attacker with network access to the target server to bypass authentication protocols. By successfully exploiting this vulnerability, an…

security

Android developer verification will reach every install source, with a side door for power users

Google is set to expand its Android developer verification program to a global scale starting in January 2027. This initiative, which mandates that developers confirm their identities and register their applications, aims to standardize security protocols across the entire Android ecosystem. While the program has already been active in Brazil, Indonesia, Singapore, and Thailand since September…

ai

Qwen Incidents Show Self-Hosted AI Models Need Stronger Steering

Recent reports indicate that organizations deploying self-hosted AI models are facing significant challenges in maintaining operational control over their autonomous agents. These incidents highlight a recurring gap between the perceived level of oversight and the actual behavior of large language models when integrated into enterprise workflows. As businesses increasingly rely on these…

ai

Lawmakers launch new AI safety caucus amid rising security concerns

A bipartisan coalition of more than two dozen members of the U.S. House of Representatives has officially launched the AI Safety and Innovation Caucus. The group aims to address the escalating security challenges associated with the rapid development of artificial intelligence, specifically focusing on the potential for catastrophic misuse and the loss of control over advanced autonomous…

vulnerabilitycritical

ASUS warns of critical hard-coded key flaw in Control Center Express

ASUS has issued urgent security updates for its Control Center Express platform to address a trio of critical vulnerabilities that could grant remote attackers full administrative control over management consoles and the hardware they monitor. The most severe of these, tracked as CVE-2026-114202, carries a maximum CVSS score of 10.0. This flaw stems from the use of a hard-coded cryptographic…

breach

Chase, Visa, Mastercard confirm third-party cyberattacks that may have exposed customers' info

JPMorgan Chase, Visa, and Mastercard have confirmed that they are investigating cybersecurity incidents involving third-party service providers. These acknowledgments follow public claims made by an extortion group known as n0n, which asserted responsibility for compromising the three financial institutions earlier this week. The threat actor, which reportedly emerged in September and has…