CVE-2026-48160: CWE-506: Embedded Malicious Code in dai-shi react-tracked
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.
AI Analysis
Technical Summary
CVE-2026-48160 describes a supply chain attack in the react-tracked repository where malicious commits were introduced into the default branch for less than a day. These commits added a postinstall script that fetched and executed remote attacker-controlled JavaScript code with disabled TLS verification, allowing remote code execution on developer machines during npm install. The attack was designed to avoid execution in CI and cloud environments, focusing on developer workstations. Although the malicious commits were removed by force-push, local clones, forks, and direct SHA references may still contain the malicious code. The second-stage payload is unavailable, but full compromise of the affected machine is assumed. The package was never published to npm, limiting exposure to those who installed from the compromised repository.
Potential Impact
Successful exploitation results in remote code execution on developer machines with the permissions of the user running npm install. This can lead to full compromise of the developer environment, including access to credentials and other sensitive data accessible to Node processes. Since the malicious code disables TLS verification and executes attacker-hosted payloads, it can bypass typical network security controls. The attack specifically targets developer workstations, potentially compromising development environments and any credentials or systems accessible from them.
Mitigation Recommendations
The malicious commits were removed by force-push, but no official patch or remediation is provided. Users who ran npm install against the affected repository between 2026-05-18 19:26:36 and 2026-05-19 15:22:45 on developer machines should treat those machines as compromised. Recommended actions include rotating all credentials accessible from the compromised machine, auditing account activity since the compromise date, and cleaning or rebuilding local clones and forks of the repository. Since the package was not published to npm, avoid installing react-tracked from untrusted sources or direct SHAs. Monitor for any suspicious activity related to this compromise.
CVE-2026-48160: CWE-506: Embedded Malicious Code in dai-shi react-tracked
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.
CVSS v4.0
Score 9.3critical
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48160 describes a supply chain attack in the react-tracked repository where malicious commits were introduced into the default branch for less than a day. These commits added a postinstall script that fetched and executed remote attacker-controlled JavaScript code with disabled TLS verification, allowing remote code execution on developer machines during npm install. The attack was designed to avoid execution in CI and cloud environments, focusing on developer workstations. Although the malicious commits were removed by force-push, local clones, forks, and direct SHA references may still contain the malicious code. The second-stage payload is unavailable, but full compromise of the affected machine is assumed. The package was never published to npm, limiting exposure to those who installed from the compromised repository.
Potential Impact
Successful exploitation results in remote code execution on developer machines with the permissions of the user running npm install. This can lead to full compromise of the developer environment, including access to credentials and other sensitive data accessible to Node processes. Since the malicious code disables TLS verification and executes attacker-hosted payloads, it can bypass typical network security controls. The attack specifically targets developer workstations, potentially compromising development environments and any credentials or systems accessible from them.
Mitigation Recommendations
The malicious commits were removed by force-push, but no official patch or remediation is provided. Users who ran npm install against the affected repository between 2026-05-18 19:26:36 and 2026-05-19 15:22:45 on developer machines should treat those machines as compromised. Recommended actions include rotating all credentials accessible from the compromised machine, auditing account activity since the compromise date, and cleaning or rebuilding local clones and forks of the repository. Since the package was not published to npm, avoid installing react-tracked from untrusted sources or direct SHAs. Monitor for any suspicious activity related to this compromise.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-20T23:12:43.032Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7b1b2ebf8831d539bca7ae
Added to database: 08/11/2026, 12:53:02 UTC
Last enriched: 08/11/2026, 12:55:43 UTC
Last updated: 08/12/2026, 00:41:12 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.