CVE-2026-48159: CWE-506: Embedded Malicious Code in dai-shi use-reducer-async
use-reducer-async is a React useReducer with async actions. Between 2026-05-18 16:29:52 and 2026-05-19 15:26:07, the default branch contained malicious commits da72edbde5705efcec6c62e0a3dcb73687b78dc8 through df07d5711458d8b46e11dd7afaaa21e88cafabfb 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 16:29:52 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity since 2026-05-18 16:29:52, and clean local clones.
AI Analysis
Technical Summary
CVE-2026-48159 describes a supply chain attack on the use-reducer-async React package where malicious commits were introduced into the default branch for about one day. These commits added a postinstall script that fetched and executed a remote JavaScript payload from an attacker-controlled HTTPS endpoint with disabled TLS verification. Execution was skipped on CI and cloud environments but ran on developer machines during npm install, allowing remote attacker-controlled code execution with the user's permissions. The malicious commits were removed by force-push, but local clones and forks may still contain them. The second-stage payload is unavailable, but full compromise of affected developer machines is assumed.
Potential Impact
Remote attacker-controlled code execution occurs on developer machines during npm install of an affected checkout, potentially leading to full compromise of anything accessible by the Node process running with the user's permissions. The malicious code bypasses TLS verification and executes arbitrary code fetched from an attacker-controlled server. This compromises developer workstations, potentially exposing credentials and sensitive data accessible from those machines.
Mitigation Recommendations
No official patch or remediation is currently available. The malicious commits were removed from the repository by force-push, but local clones, forks, and direct-SHA checkouts may still contain the malicious code. Users who ran npm install on an affected checkout between 2026-05-18 16:29:52 and 2026-05-19 15:26:07 should treat their machines as compromised. Recommended actions include rotating all credentials accessible from the machine, auditing account activity since the compromise date, and cleaning or rebuilding local clones to remove the malicious commits. Avoid running npm install on any local copies of the repository that may contain the malicious commits.
CVE-2026-48159: CWE-506: Embedded Malicious Code in dai-shi use-reducer-async
Description
use-reducer-async is a React useReducer with async actions. Between 2026-05-18 16:29:52 and 2026-05-19 15:26:07, the default branch contained malicious commits da72edbde5705efcec6c62e0a3dcb73687b78dc8 through df07d5711458d8b46e11dd7afaaa21e88cafabfb 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 16:29:52 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity since 2026-05-18 16:29:52, and clean local clones.
CVSS v4.0
Score 9.3critical
Affected software
dai-shi
use-reducer-async
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48159 describes a supply chain attack on the use-reducer-async React package where malicious commits were introduced into the default branch for about one day. These commits added a postinstall script that fetched and executed a remote JavaScript payload from an attacker-controlled HTTPS endpoint with disabled TLS verification. Execution was skipped on CI and cloud environments but ran on developer machines during npm install, allowing remote attacker-controlled code execution with the user's permissions. The malicious commits were removed by force-push, but local clones and forks may still contain them. The second-stage payload is unavailable, but full compromise of affected developer machines is assumed.
Potential Impact
Remote attacker-controlled code execution occurs on developer machines during npm install of an affected checkout, potentially leading to full compromise of anything accessible by the Node process running with the user's permissions. The malicious code bypasses TLS verification and executes arbitrary code fetched from an attacker-controlled server. This compromises developer workstations, potentially exposing credentials and sensitive data accessible from those machines.
Mitigation Recommendations
No official patch or remediation is currently available. The malicious commits were removed from the repository by force-push, but local clones, forks, and direct-SHA checkouts may still contain the malicious code. Users who ran npm install on an affected checkout between 2026-05-18 16:29:52 and 2026-05-19 15:26:07 should treat their machines as compromised. Recommended actions include rotating all credentials accessible from the machine, auditing account activity since the compromise date, and cleaning or rebuilding local clones to remove the malicious commits. Avoid running npm install on any local copies of the repository that may contain the malicious commits.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-20T23:12:43.031Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a7a1484bf8831d5394a8aa4
Added to database: 08/10/2026, 18:12:20 UTC
Last enriched: 08/10/2026, 18:26:16 UTC
Last updated: 09/25/2026, 03:49:33 UTC
Views: 84
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.