CVE-2025-59039: 
JavaScript vulnerability analysis and mitigation

Overview

CVE-2025-59039 is a supply chain compromise affecting Prebid Universal Creative (PUC), a widely used JavaScript API for rendering advertising formats. Version 1.17.3 of the prebid-universal-creative npm package was briefly injected with crypto-related malware as part of a broader npm account takeover campaign. The compromise also affected users pointing to the latest tag, including those loading the file via the popular jsDelivr CDN. Disclosed on September 9, 2025, the affected version has since been unpublished from npm. The vulnerability carries a CVSS v4.0 base score of 9.3 (Critical), assigned by GitHub (GitHub Advisory, Sonatype Blog).

Technical details

The root cause is classified as CWE-506 (Embedded Malicious Code): a threat actor gained unauthorized access to a developer's npm account and published a malicious version of the package containing a cryptocurrency theft payload (GitHub Advisory). This attack is part of a broader campaign (tracked by Sonatype as sonatype-2025-003716 and sonatype-2025-003727) that compromised over 20 npm packages — including chalk, debug, and duckdb — collectively downloaded more than 2 billion times per week (Sonatype Blog). The malicious payload was identical across all hijacked packages and was designed for cryptocurrency theft, with potential for harvesting API keys, tokens, and other secrets. No exploitation of a software bug was required; the attack relied entirely on the trust model of the npm registry and CDN distribution.

Impact

Any application or website that installed or loaded prebid-universal-creative version 1.17.3 — or resolved the latest tag to this version — was exposed to malicious JavaScript executing in their environment. The payload was focused on cryptocurrency theft, but the embedded backdoor also created risk of credential harvesting (API keys, tokens), persistent footholds for future attacks, and lateral movement within affected organizations (Sonatype Blog). Because the file was served via jsDelivr CDN, end users of websites loading PUC from that CDN were also potentially exposed to the malicious code in their browsers. The CVSS v4.0 assessment reflects high impact to confidentiality, integrity, and availability of the vulnerable system (GitHub Advisory).

Exploitability

No public proof-of-concept exploit is known, as the malicious code was embedded directly in the published package and activated upon installation or loading — no additional exploitation steps were required by end users. The EPSS score is approximately 0.044–0.116%, reflecting low predicted exploitation probability in the traditional sense, though the supply chain delivery mechanism means any consumer of the affected version was automatically exposed (GitHub Advisory). Sonatype researchers attributed the campaign to a threat actor pattern consistent with advanced persistent threats (APTs), noting similarities to tactics used by groups such as the Lazarus Group, though no definitive attribution was made (Sonatype Blog). The vulnerability is not listed in the CISA KEV catalog as of the time of this report.

Exploitation steps

  1. Account Takeover: The threat actor compromised a developer's npm account (likely via phishing or credential theft), gaining publish access to the prebid-universal-creative package.
  2. Malicious Version Publication: The attacker published version 1.17.3 to npm with an embedded cryptocurrency theft payload identical to that used in the broader chalk/debug campaign (sonatype-2025-003716).
  3. CDN Propagation: Because jsDelivr and other CDNs serve npm packages dynamically, the malicious version was automatically served to any site or application resolving prebid-universal-creative@latest or explicitly referencing 1.17.3.
  4. Payload Execution: When a victim's application loaded the compromised PUC script — either server-side (Node.js) or client-side (browser via CDN) — the embedded malicious code executed automatically, targeting cryptocurrency wallets and potentially harvesting secrets such as API keys and tokens.
  5. Persistence and Lateral Movement: The backdoor could establish persistent footholds, enabling further exploitation of the affected environment long after the initial compromise (Sonatype Blog, GitHub Advisory).

Indicators of compromise

  • Network: Unexpected outbound connections to cryptocurrency-related or unknown external endpoints from servers or browsers loading PUC; DNS queries or HTTP requests to domains associated with crypto wallet exfiltration infrastructure.
  • File System / Package Registry: Presence of prebid-universal-creative version 1.17.3 in node_modules, package-lock.json, or yarn.lock; SBOM entries referencing this version.
  • Logs: npm install logs or CI/CD pipeline logs showing installation of prebid-universal-creative@1.17.3 or resolution of latest to 1.17.3 around September 9, 2025; CDN access logs showing requests to jsDelivr for PUC latest or 1.17.3 on that date.
  • Process Behavior: Unexpected child processes or network activity spawned by Node.js processes running PUC; anomalous JavaScript execution in browser environments loading the compromised CDN-hosted file (Sonatype Blog).

Mitigation and workarounds

The maintainers unpublished version 1.17.3 from npm, making it no longer installable. Users who were pointing to latest or had installed 1.17.3 should immediately downgrade to version 1.17.2 (GitHub Advisory). For longer-term remediation, the Prebid.js 9 release notes provide guidance on migrating away from the deprecated workflow of using PUC or pointing to a dynamic/latest version. Any system that loaded the compromised version should be treated as potentially breached: review SBOMs, rotate credentials and API keys, and conduct incident response procedures. Enabling MFA on npm publishing accounts and pinning dependency versions to specific, verified releases are recommended preventive measures (Sonatype Blog).

Community reactions

Sonatype's Security Research Team published a detailed blog post on September 9, 2025, contextualizing the PUC compromise within a broader supply chain attack affecting over 20 npm packages — including chalk and debug — with a combined download volume exceeding 2 billion per week, calling it a sign of APT-level tactics targeting open source maintainers (Sonatype Blog). The Secret CISO newsletter highlighted the incident alongside other major breaches, underscoring community concern about the fragility of CDN-hosted JavaScript dependencies. Red Hat and GitLab both published advisories tracking the CVE, reflecting broad industry attention to the supply chain risk (Red Hat, GitLab Advisory).

Additional resources


Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

GHSA-g78f-3cr8-fhw5MEDIUM6.5
  • JavaScript logoJavaScript
  • imapflow
NoYesNov 15, 2026
GHSA-4j79-qhcg-f5wvMEDIUM6.4
  • JavaScript logoJavaScript
  • systeminformation
NoYesNov 15, 2026
GHSA-fcj7-c534-vj7fMEDIUM5.9
  • JavaScript logoJavaScript
  • find-my-way
NoNoNov 15, 2026
GHSA-chpj-828m-9wj6MEDIUM4.8
  • JavaScript logoJavaScript
  • karakeep
NoYesNov 15, 2026
GHSA-xcgp-hwgr-q92jLOW3.5
  • JavaScript logoJavaScript
  • karakeep
NoYesNov 15, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management