Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

build-react-wrappernpm

build-react-wrapper is a confirmed malicious npm package (MAL-2025-5074) that executes malicious code on install (malicious versions 1.0.0, 2.0.0, 2.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in build-react-wrapper (npm)

MAL-2025-5074
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall build-react-wrapper

Malicious versions

3 flagged
1.0.02.0.02.1.0

Indicators of compromise (SHA-256)

1e0cbf10c009a76e7d0f23222e90227424a4479decb417a9f079ea4200782ab2
f6f65f6886b57eb694e295831514d260f9158190d6a11d9d244efb6ce3df0883

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for build-react-wrapper (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging build-react-wrapper across your stack and pipelines.

  2. If you installed it — respond

    Remove build-react-wrapper from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If build-react-wrapper was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks build-react-wrapper before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. build-react-wrapper on npm has been identified as a malicious package (versions 1.0.0, 2.0.0, 2.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03104RLUA-2025-06075

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks build-react-wrapper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

build-react-wrapper (npm) malicious package — MAL-2025-5074 | O3 Security