CVE-2026-48159 dai-shi CVE debrief

Who should care

Developers 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 and take immediate action.

Why it matters

CVE-2026-48159 is a critical vulnerability in the use-reducer-async package that could lead to code execution on developer workstations during `npm install`. Developers who ran `npm install` against an affected checkout should treat their machines as compromised and take immediate action to rotate credentials, audit account activity, and clean local clones.

• Potential code execution on developer workstations during `npm install`
• Possible credential compromise and lateral movement
• Required verification of developer workstation security configurations
• Need for immediate remediation and cleanup of affected systems

Technical summary

The use-reducer-async package, a React useReducer with async actions, was compromised between 2026-05-18 16:29:52 and 2026-05-19 15:26:07. Malicious commits were added to the default branch, which 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. 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

Defensive priority

Developer workstation security is at risk due to potential code execution during `npm install`.

Recommended defensive actions

• Immediately audit and clean local clones of the affected repository
• Rotate every credential reachable from affected developer machines
• Verify and update developer workstation security configurations
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The malicious commits were removed by force-push, but local clones, forks, and direct-SHA URLs may still contain them. The package was not published to npm. 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. The second

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.