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

reactify-utilsnpm

reactify-utils is a confirmed malicious npm package (MAL-2025-48536) that executes malicious code on install (malicious versions 1.10.3, 1.10.4, 1.10.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in reactify-utils (npm)

MAL-2025-48536
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall reactify-utils

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

7 flagged
1.10.31.10.41.10.51.10.71.10.81.11.210.11.2

Indicators of compromise (SHA-256)

33fa7e90d4152416b1c914f2f869a4b26ea6afb25a672834b497be10bcea138a
d7732e768e367dc5e897903fe119f74597554b3dcdf84fe316d81f52dd4f8831
87a12d335918712bcf8acd389896efec898cf8b9474893d286201497cd51127d
fbe8faa11e271fe9f7033818fef45f45ba272de41c3845bace259ffd0318fa4c

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 reactify-utils (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reactify-utils across your stack and pipelines.

  2. If you installed it — respond

    Remove reactify-utils 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 reactify-utils 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 reactify-utils 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. reactify-utils on npm has been identified as a malicious package (versions 1.10.3, 1.10.4, 1.10.5, 1.10.7, 1.10.8, 1.11.2, 10.11.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qhvj-cv7f-cx6rRLMA-2025-05499RLUA-2025-05931RLUA-2025-06462

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks reactify-utils-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

reactify-utils (npm) malicious package — MAL-2025-48536 | O3 Security