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

react-packery-componentnpm

Advisory published Updated

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

Malicious code in react-packery-component (npm)

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

What this malware does

The package react-packery-component 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
1.0.3

Indicators of compromise (SHA-256)

872c1f39f86353dffdf61d72583e72f1519188541ac880a8d4da67645a1f0934
421ab2404a9e51da5321e4a392e5d3051bcaa94a132f2a856431503308762442
9c9dbf0ac814d8ad3cdd41ff8e2cebc7bf1bef909281eb89d019a8efd626d047

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for react-packery-component (version 1.0.3).

  2. If you installed it — respond

    react-packery-component 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-packery-component 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-packery-component on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6wgc-f4jw-23rq

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks react-packery-component-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-packery-component (npm) malicious package — MAL-2025-191414 | O3 Security