# CVE-2025-59038: Prebid.js NPM package briefly compromised

> Attackers injected malicious code into a compromised npm package to redirect cryptocurrency transactions to their wallets.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025

## What is CVE-2025-59038?

CVE-2025-59038 is a high-severity vulnerability in Prebid.js, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Prebid.js is a free and open source library for publishers to quickly implement header bidding. NPM users of prebid 10.9.2 may have been briefly compromised by a malware campaign. The malicious code attempts to redirect crypto transactions on the site to the attackers' wallet. Version 10.10.0 fixes the issue. As a workaround, it is also possible to downgrade to 10.9.1.

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2025-59038?


## How do I fix CVE-2025-59038?

Upgrade to a fixed version.

## Is CVE-2025-59038 being exploited?

There is no known exploitation of CVE-2025-59038 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59038 and fix it if it is affected.

What it is: CVE-2025-59038 is a high-severity vulnerability in Prebid.js, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-59038 in the wild and no public exploit code.

Affected product: Prebid.js. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59038/ (Markdown: https://insights.sbomify.com/CVE-2025-59038/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59038
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59038
- OSV: https://osv.dev/vulnerability/CVE-2025-59038

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59038/
Summaries are generated and may contain mistakes; the official description above is the record.