CVE-2026-48161 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-19 01:07:01 should treat the machine as compromised and take immediate action.

Why it matters

CVE-2026-48161 is a critical vulnerability in the react18-use package that could lead to code execution on developer machines during `npm install`. Developers who ran `npm install` against an affected checkout should treat the machine as compromised and take immediate action.

• Potential code execution on developer machines
• Credential compromise and potential lateral movement
• Data tampering and unauthorized access
• System compromise and potential business impact

Technical summary

The react18-use package, a React 19 use hook shim, was vulnerable to a critical exploit. Malicious commits were introduced to the default branch, executing remote attacker-controlled code on developer machines during `npm install`. Those who ran `npm install` against an affected checkout on a developer machine on or after 2026-05-19 01:07:01 should treat the machine as compromised and take immediate action. 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 1

Defensive priority

High

Recommended defensive actions

• Treat machines that ran `npm install` against an affected checkout as compromised
• Rotate every credential the machine could reach
• Audit account activity since 2026-05-19 01:07:01
• Clean local clones
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• 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.

Evidence notes

The CVE record and source item provide details about the vulnerability, including the malicious commits and the affected package. However, the second-stage payload was attacker-hosted and cannot be reconstructed.

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.