CVE-2026-48160 react-tracked was vulnerable to malicious code execution via compromised commits
Malicious commits in react-tracked executed remote code on developer machines during npm install, requiring credential rotation and machine cleanup.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-48160?
CVE-2026-48160 is a critical vulnerability in dai-shi react-tracked, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
react-tracked provides state usage tracking with Proxies. Between 2026-05-18 19:26:36 and 2026-05-19 15:22:45, the default branch contained malicious commits 6978272a7d6ca02225cb747ea69f427512e33699 through 949f1a3d6bb1ff7d1a0dec892afd773e742627e8 that executed remote attacker-controlled code on developer machines during `npm install`. The commits were removed by force-push, but local clones, forks, and direct-SHA URLs may still contain them, and `npm install` against an affected checkout will still execute the code today. The package was not published to npm. `src/install.js` was added and wired into the `postinstall` script. It fetched a JavaScript payload from an attacker-controlled HTTPS endpoint (configurable via an environment variable), disabled TLS verification, and evaluated the response as code with `require` available. Execution was deliberately skipped on CI and cloud/serverless environments, targeting developer workstations. The second-stage payload was attacker-hosted and cannot be reconstructed. Assume full compromise of anything reachable from a Node process with the user's permissions. Those who ran `npm install` against an affected checkout on a developer machine on or after 2026-05-18 19:26:36 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity** since 2026-05-18 19:26:36, and clean local clones.
Weakness: CWE-506
Which versions are affected by CVE-2026-48160?
How do I fix CVE-2026-48160?
No fix has been published for CVE-2026-48160 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-48160 being exploited?
There is no known exploitation of CVE-2026-48160 in the wild and no public exploit code.
Sources
Also known as GHSA-79c5-q7m9-9c6x.