What is Optimjack in Cybersecurity?
Optimjack is a large-scale web supply chain attack disclosed on November 16, 2026, in which threat actors injected malicious JavaScript into the custom "Project JavaScript" configuration field of customer accounts on the Optimizely experimentation platform, causing at least 178 major global websites—including CNN, BBC, Zoom, Salesforce, GitLab, HSBC, Equifax, IKEA, and Ledger—to unknowingly serve cryptocurrency wallet-swapping malware, payment card skimmers, and iOS mobile exploit kits directly from Optimizely's legitimate Content Delivery Network (CDN).
Because Optimizely snippets are embedded near the top of web pages to run A/B tests and execute automatically in visitors' browsers under cdn.optimizely.com's trusted TLS certificate, browsers and traditional perimeter defenses treated the poisoned payloads as trusted first-party or approved third-party code. Within roughly 17 hours before mass cleanup concluded, the attacker updated the live payload 26 times—transforming trusted enterprise websites across financial services, media, technology, retail, and aviation into silent malware delivery conduits.
Technical Mechanics: How the Optimjack Attack Operates
The Optimjack campaign illustrates a browser-layer software supply chain compromise that abuses legitimate SaaS customization features rather than breaching individual victim web servers:
Abuse of Custom Project JavaScript Fields: Optimizely Web provides a "Project JavaScript" feature that allows site administrators to bundle custom JavaScript directly into their hosted snippet file ([cdn.optimizely.com/js/](https://cdn.optimizely.com/js/)<project_id>.js). Threat actors exploited platform access to inject malicious code across 188 distinct customer snippets—including Optimizely's own main website and login portal.
Multi-Variant Obfuscation and Inline Fallback: The injected code appeared in three forms across compromised snippets: a direct <script> tag loading external payloads from 1688360[.]cc/track.js, a Base64-encoded loader hidden via atob() to evade basic string searches, and a full inline copy executed via eval() that remained functional even if corporate firewalls or DNS filters blocked the external staging domain.
Dynamic Payload Evolution: Throughout November 16, 2026, the threat actor modified the live payload 26 times, progressively adding new monetization and mobile exploitation capabilities as the campaign unfolded.
Multi-Stage Malicious Capabilities of the Optimjack Payload
Once executed inside a visitor's browser, the Optimjack JavaScript payload performed four distinct malicious operations depending on the user's device and page interactions:
Cryptocurrency Address Swapping (Crypto Clipper): The script continuously scanned the Document Object Model (DOM), form inputs, links, clipboard copy events (navigator.clipboard), and outgoing fetch/XHR network requests for valid cryptocurrency wallet addresses across Bitcoin (BTC), Ethereum (ETH and EVM chains), Solana (SOL), TRON (TRX), TON, Litecoin (LTC), Bitcoin Cash (BCH), and Dogecoin (DOGE). Using chain-specific checksum validation to ensure swaps would not fail wallet formatting checks, it replaced legitimate addresses near payment keywords with attacker-controlled wallet addresses.
Payment Card Skimming (Magecart-Style Harvesting): Added mid-campaign, a secondary module hooked form submissions and fetch/XHR POST requests to capture credit and debit card numbers (validated via the Luhn algorithm), expiration dates, and CVV codes typed into site-controlled checkout fields, exfiltrating the stolen payment data via navigator.sendBeacon.
DOM Screenshot and Session Cookie Exfiltration: Immediately after swapping a cryptocurrency address on a visible page element, the script dynamically loaded html2canvas.min.js, rendered a JPEG screenshot of the victim's visible browser screen, and transmitted the image alongside the page URL and non-HttpOnly document.cookie values to the attacker's collection endpoint.
Targeted iOS Exploit Kit Delivery (Coruna and DarkSword): When the script detected an iPhone, iPad, or iPod user agent, it loaded secondary stage scripts that fingerprinted the device's iOS version and injected hidden iframes delivering the Coruna exploit chain (targeting iOS 13 through 17) or the DarkSword exploit chain (targeting iOS 18.x up to 18.6).
Why Traditional Defenses Failed to Block Optimjack
Optimjack exposed critical architectural blind spots in how enterprises govern third-party JavaScript and client-side attack surfaces:
Trusted CDN Origin Bypassed Content Security Policy (CSP): Because the poisoned script was served directly from Optimizely's authentic CDN (cdn.optimizely.com), organizations whose CSP script-src allowlists trusted cdn.optimizely.com—or used 'strict-dynamic' and 'unsafe-eval' directives—permitted the malicious payload to execute without generating CSP violations.
Subresource Integrity (SRI) Incompatibility: Because A/B testing and experimentation snippets are dynamically updated by marketing and product teams, organizations rarely apply static Subresource Integrity (SRI) cryptographic hashes to those <script> tags.
Zero Visibility from Server-Side Telemetry: Because the malicious code executed entirely inside visitors' browsers via a third-party CDN call, internal web server logs, host-based Endpoint Detection and Response (EDR) agents, and perimeter Web Application Firewalls (WAFs) saw no anomalous server-side traffic.
How to Detect, Mitigate, and Remediate Optimjack Exposure
Organizations and end users affected by Optimjack or similar third-party script supply chain attacks must take immediate client-side and vendor governance actions:
Audit Third-Party Scripts and Custom JavaScript Configurations: Inspect all Optimizely projects and experiment configurations for unauthorized changes, Base64 atob() strings, references to 1688360[.]cc, or unfamiliar custom JavaScript, and request full project-level change logs from the vendor.
Rotate Vendor API Tokens and Enforce Least-Privilege Access: Review all user accounts, API keys, and CI/CD integrations with write permissions to tag managers and experimentation platforms, revoking and rotating credentials immediately.
Harden Content Security Policy (CSP) Directives: Remove 'unsafe-eval' from script-src policies and implement strict connect-src directives that explicitly restrict outbound browser fetch, XHR, and sendBeacon connections to approved first-party endpoints.
Isolate Payment Forms Using Cross-Origin Iframes: Ensure payment card fields are hosted inside isolated, PCI-compliant cross-origin payment iframes (such as Stripe Elements or Adyen) so third-party JavaScript executing on the parent page cannot read sensitive cardholder inputs.
Protect End-User Devices and Financial Accounts: Visitors who interacted with affected websites on November 16, 2026, should immediately update iPhones and iPads to iOS 18.7.3 or iOS 26.3 or later, verify cryptocurrency transaction histories against destination addresses, and monitor or replace payment cards entered on impacted sites.
Frequently Asked Questions
How did Optimjack infect major websites without breaching their web servers?
Optimjack was a browser-layer supply chain attack. Attackers injected malicious JavaScript into the custom "Project JavaScript" field of customer accounts on Optimizely. Because hundreds of major websites embed Optimizely snippets directly from cdn.optimizely.com, visitors' browsers automatically downloaded and executed the tampered script as trusted code.
Did allowlisting cdn.optimizely.com in a Content Security Policy stop Optimjack?
No. Because the malicious JavaScript was bundled inside the legitimate script hosted on cdn.optimizely.com, allowlisting that CDN domain permitted the initial loader to run. Strict connect-src rules blocking unauthorized exfiltration domains and eliminating 'unsafe-eval' are required to contain payloads delivered through trusted third-party script hosts.
Why did Optimjack target iPhones and iPads specifically?
In addition to stealing cryptocurrency and payment cards from desktop and mobile visitors, the Optimjack script inspected browser user-agent strings to deliver hidden iframes containing the Coruna and DarkSword iOS exploit kits to unpatched iPhones and iPads running iOS 18.6 or earlier.
How can organizations prevent similar third-party JavaScript supply chain attacks?
Organizations should maintain a continuous inventory of all third-party scripts executing on public, login, wallet, and checkout pages; enforce strict CSP connect-src policies; isolate payment forms inside cross-origin iframes; mark authentication cookies as HttpOnly; and monitor external web assets for unauthorized script changes.
Immediate Actionable Optimjack Defense Checklist
Inventory All Third-Party Scripts on Public and Transactional Pages: Map every external JavaScript snippet (experimentation platforms, tag managers, analytics, and chat widgets) executing across public, login, wallet, and checkout flows.
Audit Experimentation and Tag Manager Accounts: Inspect custom JavaScript fields for unauthorized atob(), eval(), or unknown external domains, and rotate all platform API keys and administrative credentials.
Enforce Strict CSP connect-src and Remove 'unsafe-eval': Restrict outbound browser connections (fetch, XHR, sendBeacon) to explicitly approved domains and eliminate 'unsafe-eval' from script-src policies.
Isolate Payment Fields and Protect Session Cookies: Verify that payment card inputs run inside isolated cross-origin payment iframes and ensure all authentication cookies carry the HttpOnly and Secure flags.
Deploy Client-Side Script Behavior Monitoring and Mobile Patching: Continuously monitor external web properties for unexpected child script injections and enforce mobile device management (MDM) updates to iOS 18.7.3 or iOS 26.3 or later across corporate fleets.
How ThreatNG Solves Optimjack and Third-Party JavaScript Supply Chain Risks
ThreatNG operationalizes defense against Optimjack and client-side JavaScript supply chain attacks by functioning as an unauthenticated external scout that delivers The Connectorless Ground Truth. Unifying External Attack Surface Management (EASM), Digital Risk Protection (DRP), and continuous Security Ratings into a single platform, ThreatNG discovers, evaluates, categorizes, and monitors an enterprise’s public-facing web applications, embedded third-party JavaScript snippets, Content Delivery Network (CDN) dependencies, Content Security Policy (CSP) headers, and leaked SaaS API credentials strictly from an adversary-centric perspective.
Disclosed on November 16, 2026, Optimjack compromised custom "Project JavaScript" fields across 188 customer accounts on the Optimizely experimentation platform—causing at least 178 major global websites to silently serve cryptocurrency wallet-swapping malware, payment card skimmers, session cookie harvesters, and iOS exploit kits (Coruna and DarkSword) directly from Optimizely's legitimate CDN (cdn.optimizely.com). Because the malicious code was bundled inside a trusted third-party script host and executed entirely inside visitors' browsers, server-side Web Application Firewalls (WAFs), host-based Endpoint Detection and Response (EDR) sensors, and basic domain allowlists failed to detect or block the compromise.
Operating strictly from the outside looking in, ThreatNG requires zero internal software agents, API keys, internal credentials, or pre-configured asset registries. Rather than generating uncontextualized lists of web domains or theoretical alerts, its proprietary DarChain engine links disparate technical discoveries—connecting public web properties embedding third-party experimentation or tag-management scripts directly to missing HTTP security headers, leaked vendor API tokens in public code repositories, and dark web threat telemetry. By pinpointing foundational Attack Path Choke Points and delivering Legal-Grade Attribution, ThreatNG equips application security teams, fraud investigators, third-party risk managers, and security operations centers (SOCs) with deterministic proof to see what threat actors see, inventory client-side script supply chains, harden browser execution boundaries, and neutralize web skimming and crypto-clipping vectors before customers are compromised.
External Discovery for Client-Side JavaScript Supply Chains and SaaS Dependencies
Defending against Optimjack-style web supply chain compromises requires an autonomous discovery tier capable of cataloging every internet-facing web application, embedded third-party JavaScript dependency, tag manager, CDN routing chain, and leaked vendor API secret across the global internet without internal assistance or manual seed configuration. ThreatNG establishes this authoritative baseline through connectorless external discovery.
Third-Party Dependency & SaaS Mapping (SaaSqwatch): Evaluates public digital exhaust—such as embedded tracking scripts, external JavaScript references, DNS Canonical Name (CNAME) routing chains, HTTP response headers, and SSL/TLS certificates—to map third-party hosted software, experimentation platforms (such as Optimizely), tag managers, analytics providers, payment gateways, and CDNs across all public web properties. This constructs an external dependency graph revealing exactly which corporate domains, login portals, and checkout flows embed third-party script snippets.
Connectorless Asset & Perimeter Inventory: Maps an organization's complete public-facing digital perimeter using unauthenticated discovery with zero internal connectors, software agents, or network credentials. By analyzing authoritative Domain Name System (DNS) zone files, public domain registries, SSL/TLS certificate transparency logs, Regional Internet Registry (RIR) databases, and global Border Gateway Protocol (BGP) routing announcements, ThreatNG catalogs every public domain, subdomain, e-commerce portal, and web application where third-party JavaScript executes.
Patented Recursive Discovery for Shadow Web Properties and Marketing Microsites: Starting from an initial corporate seed (such as an apex domain, brand name, or ASN), ThreatNG iteratively expands outward. As new subdomains, netblocks, or DNS records emerge, the engine feeds them back in as fresh discovery seeds—uncovering forgotten marketing landing pages, regional storefronts, and customer support microsites running unmonitored tag managers or experimentation scripts outside central security governance.
Non-Human Identity (NHI) and Leaked Vendor API Key Discovery: Continuously scans public version control systems (such as GitHub, GitLab, and Bitbucket), paste repositories (such as Pastebin), and developer discussion forums for exposed machine secrets. ThreatNG uncovers hardcoded experimentation platform API tokens, tag-manager personal access tokens, CDN purge keys, and frontend webhook secrets committed by developers or external marketing agencies—the exact credentials attackers steal to inject malicious custom JavaScript into third-party SaaS accounts.
Associated Organizations Discovery ("Opportunity Finder"): Automatically uncovers legacy subsidiaries, newly acquired operating entities, joint ventures, and dormant corporate units tied to the enterprise, ensuring acquired brand websites embedding third-party A/B testing or analytics scripts are discovered and governed.
Mobile Application Asset Discovery and App Store Enumeration: Discovers and inventories corporate-branded mobile applications across official marketplaces (Apple App Store, Google Play Store) and alternative APK repositories, identifying mobile webviews and embedded SDKs that load external third-party scripts or route users to web payment flows.
Algorithmic Permutation Discovery for Lookalike Skimming Domains: Computes and evaluates mathematical mutations of corporate brand names and checkout portals across global domain registries, uncovering attacker-controlled exfiltration domains and lookalike skimming infrastructure staged to receive stolen payment card or wallet telemetry.
External Assessment for Deterministic Client-Side and Script Exposure Evaluation
ThreatNG elevates client-side web supply chain security from blind vendor trust to deterministic, evidence-backed evaluation using its Known Vulnerability Exposure Verification (KVEV) engine, proprietary Security Ratings, and the transparent DarcRadar scoring model.
Detailed Assessment Example 1: Web Application Hijack Susceptibility and Content Security Policy (CSP) Assessment: In the Optimjack attack, websites whose CSP policies lacked strict connect-src directives or included 'unsafe-eval' in script-src permitted injected inline scripts to execute and exfiltrate stolen payment card numbers, DOM screenshots, and cookies to external attacker endpoints. ThreatNG inspects every discovered public web application, login portal, and checkout page from the outside looking in for missing or weak HTTP security headers—specifically evaluating subdomains missing Content-Security-Policy (CSP), frame-ancestors, X-Frame-Options, X-Content-Type-Options, and HTTP Strict Transport Security (HSTS). It calculates a dedicated A through F Web Application Hijack Susceptibility rating via DarcRadar, delivering empirical proof of which web properties lack browser-level containment against malicious third-party JavaScript execution and unauthorized outbound data beacons.
Detailed Assessment Example 2: Supply Chain & Third-Party Exposure Assessment on Script Dependencies: ThreatNG calculates a dedicated A through F Supply Chain & Third-Party Exposure Security Rating via DarcRadar derived entirely from unauthenticated external discovery. By evaluating external SaaS integrations, embedded JavaScript tags, DNS CNAME pointers, and CDN/proxy dependencies across the entire web perimeter, ThreatNG quantifies client-side concentration risk—identifying when dozens of corporate and subsidiary domains depend on a single third-party experimentation or tag-management script host.
Detailed Assessment Example 3: Non-Human Identity (NHI) Exposure and SaaS Script Injection Blast Radius: Threat actors frequently compromise third-party SaaS accounts (such as experimentation platforms or tag managers) by harvesting leaked API tokens or CI/CD credentials committed to public repositories by developers or digital marketing agencies. When ThreatNG discovers an exposed SaaS API token or frontend deployment secret on GitHub or Pastebin, it evaluates the technical parameters of the credential and assigns an A through F Non-Human Identity (NHI) Exposure rating via DarcRadar—quantifying how an attacker can authenticate into the vendor console and inject malicious JavaScript across every connected corporate website.
Detailed Assessment Example 4: Subdomain Takeover Susceptibility on Dangling Script and Analytics CNAMEs: Marketing and analytics teams routinely map subdomains (such as metrics.company.com, track.firm.com, or experiments.brand.com) via DNS CNAME records to third-party SaaS platforms to serve first-party-scoped tracking scripts. When a vendor contract expires while the CNAME remains active, ThreatNG cross-references discovered subdomains across multi-cloud environments against a catalog of over 60 cloud services to verify whether the underlying host is unclaimed. When an authoritative CNAME points to an unclaimed resource, ThreatNG assigns an immediate F Subdomain Takeover Susceptibility rating via DarcRadar, proving that an adversary can claim the abandoned endpoint and serve malicious JavaScript directly under the enterprise's authentic apex domain.
Detailed Assessment Example 5: Data Leak Susceptibility on Public Cloud Buckets Hosting Frontend Assets: Organizations frequently host custom JavaScript bundles, static web assets, or source maps inside public cloud storage buckets (such as AWS S3, Azure Blob, or Google Cloud Storage). ThreatNG evaluates public cloud storage instances for unauthenticated read and write permissions, assigning an A through F Data Leak Susceptibility rating via DarcRadar to prevent attackers from overwriting hosted JavaScript files or inspecting exposed source maps to craft targeted DOM-scraping payloads.
Strategic Reporting for Client-Side Governance, PCI DSS Compliance, and Audit Defensibility
ThreatNG standardizes the communication of web supply chain and client-side script exposures by converting raw outside-in telemetry, dependency graphs, and HTTP security header evaluations into structured, auditable records designed for application security teams, PCI DSS compliance officers, legal counsel, and corporate boards.
Executive Security Ratings Reports: Converts complex web header gaps, third-party script dependencies, and leaked machine secrets into standardized A through F security ratings across categories including Web Application Hijack Susceptibility, Supply Chain & Third-Party Exposure, Cyber Risk Exposure, Data Leak Susceptibility, and Non-Human Identity (NHI) Exposure. Using the transparent, penalty-based DarcRadar formula, ThreatNG provides objective ratings backed by deterministic evidence.
Correlation Evidence Questionnaires (CEQs): ThreatNG dynamically generates Correlation Evidence Questionnaires based on confirmed external discoveries. The CEQ acts as an EASM-to-Audit Translation Layer, transforming unauthenticated outside-in discoveries—such as a checkout subdomain missing strict CSP headers or embedding unmonitored third-party scripts—into targeted, auditable inquiries mapped directly to regulatory frameworks (including PCI DSS v4.0.1 Requirements 6.4.3 and 11.6.1 governing payment page script inventory, authorization, integrity, and tamper detection) across four functional pillars: Technical, Strategic, Operational, and Financial.
Unified External Exposure Display and Report: Consolidates External Attack Surface Management, Digital Risk Protection, and Security Ratings into a single, cohesive engine. This connectorless capability automatically chains isolated discoveries into end-to-end exploit scenarios via DarChain, handing engineering and compliance teams a prioritized blueprint for client-side hardening.
Forensic Evidence Packages and Legal-Grade Attribution: When ThreatNG verifies missing CSP protections, unauthorized third-party script redirects, a dangling analytics CNAME, or a leaked vendor API key, it compiles a comprehensive forensic evidence package containing timestamped technical markers, affected URLs, HTTP response headers, DNS resolution histories, and Legal-Grade Attribution. This documentation supports rapid engineering remediation, vendor incident inquiries, and regulatory compliance audits.
External Adversary View and Regulatory Compliance Mapping: Automatically correlates raw external web discoveries into strategic narratives aligned with MITRE ATT&CK for Enterprise (Initial Access: T1195.002 Compromise Software Supply Chain, T1189 Drive-by Compromise; Collection: T1056.003 Web Portal Capture, T1113 Screen Capture, T1115 Clipboard Data; Credential Access: T1539 Steal Web Session Cookie), NIST CSF 2.0 (Govern, Identify, Protect), and PCI DSS v4.0.1.
U.S. SEC Cybersecurity Disclosures Report: Connects material external supply chain compromises, payment skimming exposures, and systemic web governance gaps directly to corporate regulatory filings (such as Form 10-K Item 106 and Form 8-K), documenting continuous technical due diligence for executive leadership.
Continuous Monitoring of Third-Party Script Drift and HTTP Header Degradation
Because marketing teams continuously deploy new experimentation snippets, tag managers dynamically load downstream scripts, and DevOps deployments frequently overwrite HTTP response headers, point-in-time web audits fail to detect client-side supply chain risks. ThreatNG delivers 24/7 continuous external surveillance across global web perimeters, cloud environments, public code repositories, and underground channels.
The platform tracks asset state changes, newly added third-party SaaS scripts, degraded or missing Content Security Policy (CSP) headers, modified DNS CNAME chains, fresh SSL/TLS certificate issuances, and newly leaked API tokens in real time. If a site update removes strict connect-src CSP directives on a checkout or wallet page, or if a marketing team embeds an unapproved third-party script on a login portal, ThreatNG detects the drift immediately.
Furthermore, ThreatNG incorporates its Overwatch capability—a cross-entity intelligence system that instantly evaluates exposure across an entire portfolio of corporate subsidiaries, acquired brands, and regional storefronts whenever a widespread web supply chain incident like Optimjack is disclosed. Overwatch pinpoints every corporate and subsidiary web property embedding the affected third-party vendor within seconds, enabling immediate fleet-wide containment.
Investigation Modules for Client-Side Supply Chain and Credential Path Analysis
ThreatNG features specialized investigation modules that allow application security engineers, fraud analysts, and incident responders to trace third-party script dependencies, investigate leaked SaaS tokens, and map multi-step client-side attack paths.
Detailed Module Example 1: The DarChain Exploit Path Mapping Engine: DarChain (Digital Attack Risk Contextual Hyper-Analysis Insights Narrative) chains isolated technical, credential, and environmental discoveries into predictive attack graphs. For example, DarChain maps how an attacker uncovers a leaked experimentation platform API key committed by a marketing contractor in a public GitHub repository, correlates that credential with corporate checkout and wallet subdomains identified via SaaSqwatch as embedding the vendor's CDN script, and models how missing Content-Security-Policy headers on those subdomains allow injected JavaScript to execute eval(), swap cryptocurrency wallet addresses, skim payment cards, and exfiltrate non-HttpOnly session cookies. Instead of presenting disconnected alerts, DarChain pinpoints the critical Attack Path Choke Point—such as rotating the leaked vendor API key, enforcing strict CSP connect-src rules without 'unsafe-eval', and isolating payment inputs—proving that eliminating those specific nodes collapses the entire client-side attack path.
Detailed Module Example 2: SaaSqwatch Technology Stack & SaaS Identification Module: Operating as ThreatNG's external SaaS and dependency intelligence engine, SaaSqwatch inspects web exhaust, embedded script signatures, HTTP headers, and DNS records across every discovered subdomain to catalog all third-party experimentation tools, tag managers, analytics scripts, and payment processors—giving security teams complete visibility into their client-side software supply chain.
Detailed Module Example 3: Sensitive Code Exposure Module: Continuously monitors public version control platforms (GitHub, GitLab, Bitbucket) and paste sites (Pastebin) for leaked corporate secrets. This module uncovers hardcoded experimentation platform API tokens, tag manager keys, CDN credentials, and frontend source code committed by developers or agencies, capturing exact repository URLs and commit timestamps so teams can revoke compromised tokens before attackers hijack third-party script configurations.
Detailed Module Example 4: Subdomain Infrastructure Exposure Module: Inspects discovered domains and subdomains for missing HTTP security headers (CSP, HSTS, X-Frame-Options), dangling CNAME records, and unmonitored shadow web portals—identifying every public web surface susceptible to client-side script injection or UI redressing.
Detailed Module Example 5: Dark Web Presence and Infostealer Intelligence: Operating through its dark web intelligence modules, ThreatNG continuously monitors underground marketplaces, hacker forums, paste sites, and infostealer malware logs for compromised SaaS administrator logins, session cookies, and active Magecart/crypto-clipper campaign chatter—alerting defenders when credentials controlling corporate tag managers or experimentation consoles appear in stealer logs.
Detailed Module Example 6: Cybersecurity AI Prompts (DarcPrompt): DarcPrompt packages verified web supply chain findings, SaaSqwatch script inventories, and DarChain attack paths into structured prompt blueprints. Featuring specialized personas—such as External Attack Paths, Identity and Access Exposure, and External GRC Assessment—DarcPrompt applies strict architectural constraints that bind AI reasoning to ThreatNG's proprietary ground truth. Through an Air-Gapped Handoff, application security and compliance teams safely copy these blueprints into their internal private enterprise AI systems to draft strict Content Security Policy headers, PCI DSS v4.0.1 compliance documentation, and vendor incident questionnaires without exposing sensitive telemetry to public AI services.
Intelligence Repositories for Web Supply Chain and Fraud Context
ThreatNG centralizes and structures threat intelligence through the DarCache intelligence engine, providing an interconnected dynamic ecosystem of specialized repositories that grounds client-side defense in empirical adversary reality:
DarCache BIN: Dedicated repository monitoring Bank Identification Numbers (BINs) to identify and prevent potential payment card fraud across digital transactional and e-commerce assets—alerting financial and fraud teams when payment card numbers harvested by Magecart or Optimjack-style web skimmers surface in underground carding markets.
DarCache Infostealer: Parses dark web logs, Telegram channels, and illicit cloud archives for compromised corporate credentials, SaaS administrator logins, session cookies, and Primary Refresh Tokens (PRTs)—detecting when marketing or engineering credentials with write access to tag managers or experimentation platforms are stolen by infostealer malware.
DarCache Dark Web & Rupture: Scans underground forums, paste sites, and dark web sources for threats to brand assets, domains, and customer data, tracking web-skimming kits, stolen session cookie dumps, and compromised vendor disclosures.
DarCache Vulnerability & eXploit: Integrates NVD baselines, CISA KEV listings, 30-day EPSS probabilities, and verified PoC exploit pointers to evaluate whether web servers, reverse proxies, or mobile platforms (such as unpatched iOS webviews targeted by Coruna and DarkSword exploit chains) face active exploitation.
DarCache Mobile: Detects hardcoded access credentials, third-party SDK keys, and backend endpoints within public mobile applications, uncovering mobile apps that load external web scripts or payment flows.
DarCache Bug Bounty: Aggregates and analyzes historical bug bounty program disclosures and crowdsourced exploit patterns to evaluate which public web applications, login portals, and checkout domains are under active scrutiny by external researchers.
DarCache Ransomware: Tracks active ransomware cartels, extortion leak portals, and their specific tactics, techniques, and procedures (TTPs), monitoring whether extortion groups leverage compromised web supply chains or stolen session tokens for initial access.
DarCache 8-K & ESG: Tracks SEC Form 8-K filings, global ESG violations, and corporate regulatory disclosures, providing non-technical governance indicators that connect material supply chain breaches and consumer data compromises to board oversight.
Cooperation with Complementary Solutions
ThreatNG functions as an external intelligence scout that cooperates seamlessly with complementary solutions across application security, network defense, fraud prevention, and security operations to contain Optimjack and client-side script supply chain attacks.
Cooperation with Client-Side Security and Script Integrity Monitoring Platforms: ThreatNG discovers all public-facing domains, shadow marketing microsites, and acquired subsidiary web properties embedding third-party JavaScript via SaaSqwatch and recursive discovery. It feeds this complete outside-in web inventory into complementary solutions (enterprise client-side security and PCI DSS 6.4.3 / 11.6.1 script monitoring platforms), ensuring behavioral script monitors cover every live web property rather than only primary corporate domains.
Cooperation with Web Application Firewalls (WAF) and Content Delivery Networks (CDNs): ThreatNG identifies web applications and checkout subdomains missing strict Content-Security-Policy (CSP), connect-src, frame-ancestors, and X-Frame-Options headers. It passes these findings into complementary solutions (enterprise WAF and CDN edge platforms). Security teams deploy edge header-injection rules—enforcing strict CSP connect-src allowlists and removing 'unsafe-eval' at the CDN edge to block unauthorized JavaScript execution and outbound data exfiltration without waiting for application code deployments.
Cooperation with Protective DNS Resolvers and Secure Web Gateways (SWGs): ThreatNG identifies malicious exfiltration domains, crypto-clipper endpoints, and lookalike skimming infrastructure. It passes these indicators into complementary solutions (enterprise protective DNS resolvers and SWGs) to block corporate users and managed mobile devices from resolving or transmitting data to external attacker collection servers.
Cooperation with Identity and Access Management (IAM) and Enterprise Secrets Vaults: ThreatNG passes verified leaked SaaS API tokens, experimentation platform credentials, and compromised marketing administrator session cookies discovered in Sensitive Code Exposure or DarCache Infostealer to complementary solutions (enterprise IAM platforms and secrets management vaults). The IAM platform and secrets vault immediately revoke active sessions, rotate API keys, and enforce phishing-resistant FIDO2 authentication on third-party SaaS consoles so attackers cannot inject malicious custom JavaScript.
Cooperation with Security Orchestration, Automation, and Response (SOAR): ThreatNG delivers pre-correlated Context Objects, forensic evidence packages, and DarChain attack paths to complementary solutions (enterprise SOAR platforms) via an API. The SOAR platform acts as the automated execution engine—translating ThreatNG’s verified web supply chain findings into automated playbooks that apply emergency CDN CSP headers, block exfiltration domains, rotate exposed vendor tokens, and route tickets to web engineering owners.
Cooperation with Mobile Device Management (MDM) and Unified Endpoint Management (UEM): Because Optimjack payloads selectively deliver iOS exploit kits (Coruna and DarkSword) to unpatched mobile browsers visiting compromised websites, ThreatNG feeds active web supply chain exploit intelligence into complementary solutions (enterprise MDM/UEM platforms) to accelerate mandatory mobile OS security updates across corporate iPhone and iPad fleets.
Cooperation with Third-Party Risk Management (TPRM) and GRC Platforms: ThreatNG feeds empirical outside-in technical evidence, SaaSqwatch script dependency maps, and Correlation Evidence Questionnaires (CEQs) into complementary solutions (enterprise TPRM and GRC platforms) to track vendor script dependencies and maintain continuous PCI DSS v4.0.1 audit readiness.
Examples of ThreatNG Helping Organizations
Rapid Fleet-Wide Identification and Containment During an Optimjack-Style CDN Compromise: Immediately following the November 16, 2026 disclosure that malicious JavaScript had been injected into custom experimentation snippets served from a major third-party CDN, a global e-commerce and financial services enterprise needed to determine which of its 60 corporate and acquired subsidiary websites embedded the compromised script and whether customer payment or wallet inputs were exposed. Using ThreatNG’s Overwatch capability and SaaSqwatch technology stack module, the security team queried its pre-mapped external perimeter within seconds. ThreatNG identified nine public web properties—including two regional checkout portals and an acquired fintech wallet interface—embedding the affected CDN script, and flagged that three of those portals lacked strict Content-Security-Policy connect-src directives (earning D Web Application Hijack Susceptibility ratings). Armed with ThreatNG’s forensic evidence packages and Correlation Evidence Questionnaires (CEQs), the web engineering team immediately suspended the external script tag on transactional pages, enforced strict edge CSP headers, and audited vendor account logs within two hours.
Preventing Custom Script Injection by Revoking a Leaked Experimentation API Token: During continuous external surveillance, ThreatNG’s Sensitive Code Exposure module discovered a public GitHub repository maintained by a digital marketing contractor containing a hardcoded API token for the enterprise's web experimentation platform alongside deployment scripts for the primary corporate website. ThreatNG’s DarChain engine correlated the leaked token with the corporate web properties identified by SaaSqwatch as running the platform's snippet, demonstrating how an external adversary could use the exposed key to inject malicious JavaScript directly into the live production site. ThreatNG pinpointed the leaked API token as the critical Attack Path Choke Point. The security team rotated the token and enforced FIDO2 authentication on the vendor platform within 30 minutes, preventing an account-level supply chain compromise.
Examples of ThreatNG Working with Complementary Solutions
Working with SOAR, WAF/CDN, and Protective DNS to Contain Malicious Third-Party Script Execution: ThreatNG’s SaaSqwatch and Overwatch modules detect that an active third-party web script compromise affects five corporate subdomains, three of which are missing strict Content-Security-Policy connect-src protections. ThreatNG transmits a pre-correlated Context Object and forensic evidence package to complementary solutions (an enterprise SOAR platform). The SOAR platform executes an automated response playbook:
Dispatches an API call to complementary solutions (an enterprise WAF and CDN platform) to inject an emergency Content-Security-Policy header blocking 'unsafe-eval' and restricting connect-src outbound requests strictly to approved first-party domains across all five subdomains.
Updates complementary solutions (enterprise protective DNS resolvers) to sinkhole known malicious exfiltration domains associated with the campaign.
Opens an urgent PCI DSS 11.6.1 investigation ticket in complementary solutions (an enterprise GRC platform) with attached ThreatNG forensic evidence, neutralising client-side data exfiltration in under ten minutes.
Working with Secrets Vaults and Client-Side Security Platforms to Harden Payment Pages: ThreatNG’s Sensitive Code Exposure module uncovers an exposed tag-manager API key in a public repository, while Subdomain Intelligence identifies two newly launched promotional checkout subdomains missing frame-ancestors and CSP headers. ThreatNG passes these verified findings into complementary solutions (an enterprise secrets vault and a client-side script integrity monitoring platform). The secrets vault immediately revokes and rotates the exposed tag-manager key, while the client-side monitoring platform onboards the two newly discovered checkout subdomains into continuous script behavior surveillance and enforces isolated cross-origin payment frames.
Frequently Asked Questions
Why do traditional perimeter firewalls and WAFs miss Optimjack attacks, and how does ThreatNG help?
Traditional server-side WAFs inspect inbound HTTP requests hitting an organization's own web servers. In an Optimjack attack, the victim's browser downloads poisoned JavaScript directly from a trusted third-party CDN (cdn.optimizely.com), executing the malware client-side without touching the enterprise's web servers. ThreatNG solves this from the outside looking in by mapping every web property embedding third-party scripts via SaaSqwatch, auditing Content-Security-Policy headers that restrict outbound browser exfiltration, and detecting leaked vendor API tokens in public repositories.
How does ThreatNG help organizations comply with PCI DSS v4.0.1 Requirements 6.4.3 and 11.6.1?
PCI DSS v4.0.1 requires organizations to maintain an inventory of all payment page scripts, justify their necessity, assure their integrity, and detect unauthorized modifications. ThreatNG’s SaaSqwatch module continuously inventories external scripts across public and checkout subdomains, audits HTTP security headers via Web Application Hijack Susceptibility ratings, and generates Correlation Evidence Questionnaires (CEQs) that translate external discoveries into auditable PCI DSS governance records.
How does ThreatNG detect if an attacker can hijack our third-party experimentation or tag-manager account?
ThreatNG’s Sensitive Code Exposure module continuously scans GitHub, GitLab, Bitbucket, and Pastebin for hardcoded SaaS API keys and deployment tokens committed by developers or agencies, while DarCache Infostealer monitors dark web logs for compromised vendor administrator logins and session cookies. Detecting and revoking these credentials cuts off the primary vector attackers use to inject malicious custom JavaScript.
How fast can ThreatNG identify which corporate and subsidiary websites are affected by a third-party CDN compromise?
Through its pre-mapped external perimeter inventory, SaaSqwatch technology stack signatures, and Overwatch cross-entity intelligence system, ThreatNG evaluates all corporate domains, acquired subsidiaries, and regional storefronts within seconds—pinpointing every web property embedding an affected third-party script host so teams can respond immediately.
Immediate Actionable Optimjack and Web Supply Chain Defense Checklist
Inventory All Third-Party Scripts Across Corporate and Subsidiary Web Properties: Run ThreatNG’s SaaSqwatch and Overwatch across all apex domains and acquired entities to map every public, login, wallet, and checkout page embedding external experimentation, tag-manager, or analytics scripts.
Audit Web Properties for Missing Content Security Policy (CSP) Directives: Use ThreatNG’s Web Application Hijack Susceptibility assessment to identify subdomains missing strict Content-Security-Policy connect-src rules or permitting 'unsafe-eval', and enforce edge header protections.
Scan Public Repositories and Infostealer Logs for Leaked Vendor API Tokens: Deploy ThreatNG's Sensitive Code Exposure module and DarCache Infostealer repository to detect and rotate exposed experimentation, tag-manager, and CDN credentials.
Eliminate Dangling Analytics CNAMEs and Open Static Asset Buckets: Audit external CNAME pointers against ThreatNG’s Validated Threat Catalog of over 60 cloud services and inspect public cloud storage permissions to prevent script hijacking.
Feed Pre-Correlated Context Objects into Complementary WAF/CDN, Secrets Vault, and SOAR Platforms: Configure automated delivery of ThreatNG's verified web supply chain findings, CEQs, and DarChain attack paths into complementary WAF/CDN, protective DNS, secrets vault, and SOAR solutions to automate CSP enforcement and credential rotation.

