Third-Party JavaScript Attack Highlights CSP and Script-Monitoring Risks

Summary
A third-party web-service compromise let attackers alter customer-served JavaScript used to steal payment data, tamper with crypto transactions and expose readable cookies. Qualys outlines CSP, script-inventory and monitoring defenses.
Key points
- Attackers reportedly exploited a weakness in a third-party web platform to gain administrative control of some customer accounts and alter JavaScript served through its CDN.
- Researchers found the injected code was designed to steal payment-card details, tamper with cryptocurrency transactions and send readable cookies to attacker-controlled servers.
- A restrictive CSP can block payloads from untrusted domains, but permissive settings such as 'unsafe-eval' or trust extended through 'strict-dynamic' can weaken protection.
- The article recommends inventorying third-party scripts, removing unnecessary ones from sensitive pages, using SRI or self-hosting where practical, and monitoring script changes.
- Qualys says TotalAppSec QIDs 150206 and 150207 identify missing or weak CSP configurations, while QID 150545 identifies external JavaScript dependencies.
- Qualys describes QID 533507 as checking for references to known malicious scripts; it recommends investigating such findings and rescanning after remediation.
Article Details
- Defense Focus
- Identify third-party JavaScript exposure, detect malicious content, and limit the impact of compromised scripts.
- Detection Methods
- Inventory external JavaScript references, their URLs, and the pages that load them.
- Inspect Content Security Policy headers for missing or weak directives, including unsafe-inline, unsafe-eval, wildcard sources, and missing default-src or reporting configuration.
- Use an unauthenticated HTTP GET check to inspect response bodies for script references to known malicious scripts.
- Analyze page behavior in a vulnerable browser for unexpected file writes or process activity.
- Check pages, referenced URLs, and remotely loaded resources against public blacklists, and scan downloaded scripts and files with antivirus signatures.
- Review CSP violation reports and compare outbound requests with published indicators.
- Data Sources
- Content Security Policy headers and violation reports
- HTTP response bodies and external JavaScript references
- Page and browser behavior, including file writes and process activity
- Reputation results for pages, URLs, and remotely loaded resources
- Antivirus scan results for downloaded scripts and files
- Outbound request, web, and CDN logs
- Rule Types
- Qualys QID checks for missing or insecure CSP, external JavaScript dependencies, and references to known malicious scripts (150206, 150207, 150545, 533507)
- Heuristic signature rules for patterns such as encoded JavaScript
- Behavioral detection of unexpected file writes or processes during page rendering
- Reputation checks against public blacklists
- Antivirus signature scanning of downloaded scripts and files (QID 207003)
- Defensive Actions
- Inventory third-party scripts, the pages that load them, their internal owners, and their business purpose, including scripts added through tag managers.
- Remove unnecessary scripts, particularly from payment, login, and personal-data pages.
- Enforce a restrictive CSP with only necessary script and connection sources; avoid unsafe-eval and unsafe-inline, use nonces or hashes where possible, and enable violation reporting.
- Test CSP changes in Report-Only mode before enforcement.
- Use hosted payment fields in provider-domain iframes to keep payment entry out of reach of scripts on the page.
- Mark session and authentication cookies HttpOnly, Secure, and SameSite.
- Use Subresource Integrity or self-host scripts that change infrequently; monitor scripts that change often.
- Require script vendors to secure customer accounts and code changes; enforce MFA or SSO and limit publishing access on organizational vendor accounts.
- Monitor third-party scripts for code changes, new network destinations, and unexpected behavior.
- Keep web, CDN, and CSP logs long enough for investigation, and prepare to disable third-party scripts quickly.
- Investigate malicious-content findings, restore known-good code, rotate secrets stored in readable cookies, and rescan after remediation.
MITRE ATT&CK
T1041 · Exfiltration Over C2 ChannelThe injected code sent readable cookies to attacker-controlled servers.T1056.003 · Web Portal CaptureThe injected script was designed to capture payment card details entered into on-page forms.T1059.007 · JavaScriptMalicious JavaScript delivered through a compromised third-party script was executed in visitors' browsers.T1539 · Steal Web Session CookieThe injected code read cookies that were not marked HttpOnly.
Vendors
Products
Content Security PolicyWhat Content Security Policy can and cannot doQualys TotalAppSecHow Qualys TotalAppSec helps identify exposureQualys Web Malware DetectionDetecting malicious content with Qualys Web Malware DetectionSubresource IntegrityUse Subresource Integrity (SRI) for third-party files that change infrequently, or host them yourself.
Industries
AirlinesIn a recent incident, visitors to websites run by some of the world’s best-known brands, including news publishers, banks, airlines, and software companies, were served malicious JavaScript.SoftwareIn a recent incident, visitors to websites run by some of the world’s best-known brands, including news publishers, banks, airlines, and software companies, were served malicious JavaScript.
