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

react-dropzone-trufflenpm

Malicious code in react-dropzone-truffle (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-999
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-dropzone-truffle

What this malware does

The package react-dropzone-truffle 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.

Malicious versions

16 flagged
20.0.020.1.120.5.020.5.199.99.9100.5.0100.6.9100.11.9100.12.0100.12.5100.13.5100.19.5100.21.9100.22.9100.25.9100.27.9

Indicators of compromise (SHA-256)

f8fb0b7b6f07c6700ee7e81dec0edaa413cd2d7bce2283cb5a1a7cbfdf6eb051
deb9aafcb06b44346b4a153006bf1230d02f97d4f76ac2797f42a22005658c85
16cb75c339f5d6793d32bcbc47e29ef29d2f663d1f94388ac489cf88ebc8b638

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

  2. If you installed it — respond

    Remove react-dropzone-truffle 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 react-dropzone-truffle 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 react-dropzone-truffle 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. react-dropzone-truffle on npm has been identified as a malicious package (versions 20.0.0, 20.1.1, 20.5.0, 20.5.1, 99.99.9, 100.5.0, 100.6.9, 100.11.9, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h362-pxfp-fmhjRLMA-2026-01525

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks react-dropzone-truffle-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.

react-dropzone-truffle (npm) malicious package — MAL-2026-999 | O3 Security