CVE-2026-48161: react18-use was vulnerable to malicious code execution via compromised commits

Published Aug 10, 2026
·
Updated

react18-use is a React 19 use hook shim. Between 2026-05-19 01:07:01 and 2026-05-19 15:20:43, the default branch contained malicious commits 7b79148d1495a2505f9277da295a98cf176f4496 through 7b79148d1495a2505f9277da295a98cf176f4496 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-19 01:07:01 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity since 2026-05-19 01:07:01, and clean local clones.

Affected Software

1 affected component
npm/react18-use>=2026-05-19 01:07:01<=2026-05-19 15:20:43

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove react18-use from your environment.

    Remove/uninstall the affected `react18-use` package (it was vulnerable to malicious code execution via compromised commits and `postinstall` executes the added `src/install.js`).

  2. Operational

    Treat the developer machine as compromised if it ran `npm install` against an affected checkout on or after 2026-05-19 01:07:01; rotate every credential the machine could reach.

  3. Operational

    Audit account activity on affected developer machines since 2026-05-19 01:07:01.

  4. Operational

    Clean local clones (local clones/forks/direct-SHA URLs may still contain the malicious commits even though the default branch was force-pushed).

Event History

Aug 10, 2026
CVE Published
via MITRE·10:27 PM
Data Sourced
via MITRE·10:27 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203