CVE-2026-48158 dai-shi CVE debrief

Who should care

Developers who ran `npm install` against an affected checkout on a developer machine should treat the machine as compromised and take immediate action to rotate credentials and audit account activity.

Why it matters

This critical vulnerability requires immediate attention from developers who may have installed the affected package. The malicious code could lead to full compromise of the machine, credential theft, and lateral movement.

• Potential full compromise of machines reachable from a Node process with the user's permissions
• Credential theft and unauthorized access to sensitive data
• Lateral movement and further exploitation of the compromised machine

Technical summary

The use-context-selector package, a React useContextSelector hook in userland, was found to contain malicious commits that executed remote attacker-controlled code on developer machines during `npm install`. The vulnerability was introduced between May 18, 2026, and May 19, 2026, and was removed by force-push. However, local clones, forks, and direct-SHA URLs may still contain the malicious code. Those who ran `npm install` against an affected checkout on a developer machine should treat the machine as compromised and rotate credentials. The malicious code could lead to full compromise of the machine, credential theft, and lateral movement. The commits added a JavaScript payload that was fetched from an attack

Defensive priority

High

Recommended defensive actions

• Immediately rotate all credentials that could be accessed by the potentially compromised machine
• Audit account activity since May 18, 2026, for any suspicious behavior
• Clean local clones of the affected repository
• Verify and update the package to a secure version
• 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 vulnerability was introduced through malicious commits added to the default branch of the use-context-selector package. These commits 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.

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.