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

turbotaxnpm

Malicious code in turbotax (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-596
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall turbotax

What this malware does

The package turbotax was found to contain malicious code.

The OpenSSF Package Analysis project identified 'turbotax' @ 230.0.15 (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

2 flagged
230.0.10230.0.15

Indicators of compromise (SHA-256)

91cee2cbefbb5b64da01daccadab7ad7702807a90112c01d79fe250e054e876d
cda2e8809a84b8cce85b46ed8eeb36be232d58787fe786246c22927b05752f75
482f0494fdcfb328794613ca7098174eb93b12a55cc53cb57b73930df8ad238a

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

  2. If you installed it — respond

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

Credits

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

Detect & block this

O3 blocks turbotax-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.

turbotax (npm) malicious package — MAL-2026-596 | O3 Security