What does the turbotax malware do?

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.

Which versions of turbotax are malicious?

The following npm versions of turbotax are flagged malicious: 230.0.10, 230.0.15. Treat any of these as compromised.

How do I remediate turbotax if I installed it?

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.

I already installed turbotax — how do I know if it already compromised me?

If turbotax 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.

How do I find turbotax across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for turbotax (2 malicious versions).

Malicious package

turbotaxnpm

Advisory published Jan 29, 2026Updated Feb 2, 2026

turbotax is a confirmed malicious npm package (MAL-2026-596) that executes malicious code on install (malicious versions 230.0.10, 230.0.15). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in turbotax (npm)

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

Find it
Search your lockfiles and build artifacts for turbotax (2 malicious versions).
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.
Did it already run?
If turbotax 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. 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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database