NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

react-component-taggersnpm

Advisory published Updated

react-component-taggers is a confirmed malicious npm package (MAL-2025-190989) that steals credentials and exfiltrates sensitive data (malicious version 0.1.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-component-taggers (npm)

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

What this malware does

The package react-component-taggers was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
0.1.9

Indicators of compromise (SHA-256)

8370626a2ba2627525ecd23167c743cf429dfa292eb5f873ee6ecf282768aec6
d4b49756f82524cc17df7c04f674e36e56cb9c0f20a095b38dc9297e70440d73
52403a9d75e90b5dc32eb49c2f2f4cff9ce3038fc1f6db8b45a86aca356bb33f

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for react-component-taggers (version 0.1.9).

  2. If you installed it — respond

    react-component-taggers is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If react-component-taggers was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. react-component-taggers on npm has been identified as a malicious package (version 0.1.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7m4r-gqvv-7q3q

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks react-component-taggers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

react-component-taggers (npm) malicious package — MAL-2025-190989 | O3 Security