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

tdm-reactnpm

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

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

What this malware does

The package tdm-react was found to contain malicious code.

The OpenSSF Package Analysis project identified 'tdm-react' @ 9990.0.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

4 flagged
2.9.09990.0.09990.0.19999.0.0

Indicators of compromise (SHA-256)

38b134e4dac82a83b64836b95f28e074a84cf84fff3c2761b55f4714049b5c5e
8968a0a78c56b7d557376180f0c517c04d41f0d5679431744489211dd82d4aae
8ee3cff7ce3388bac6e66e28fbf88bb840a1fd41ae070f22c1f5d8091c2bf533
1263cd9bb27096c8c8fe4d1b9a0741f6ee2b2a908d8179514235a443178da824

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

  2. If you installed it — respond

    Remove tdm-react 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 tdm-react 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 tdm-react 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. tdm-react on npm has been identified as a malicious package (versions 2.9.0, 9990.0.0, 9990.0.1, 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06512RLUA-2026-01609

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

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

tdm-react (npm) malicious package — MAL-2025-192877 | O3 Security