Which versions of turbo-he are malicious?

The following npm versions of turbo-he are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate turbo-he if I installed it?

Remove turbo-he 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 turbo-he — how do I know if it already compromised me?

If turbo-he 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.

Is turbo-he part of a known attack campaign?

Yes — turbo-he is associated with the GHSA-6xh4-h79w-9w2q, RLMA-2026-05343 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find turbo-he across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for turbo-he (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging turbo-he across your stack and pipelines.

Malicious package

turbo-henpm

turbo-he is a confirmed malicious npm package (MAL-2026-2943) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in turbo-he (npm)

MAL-2026-2943

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall turbo-he

What this malware does

The package turbo-he 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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

6bd9985ec0cf97c08347814d88b84c1c12cd8f22507a76e2a78cacb06c6840a6

1da17bf1f37303e3d91056c1ce674462279861bc896e413f1d262548ff6b3647

497cced203ce35898bdf3cd3fca253c0917cebe7e5813725478c4fa98b0737af

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for turbo-he (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging turbo-he across your stack and pipelines.
If you installed it — respond
Remove turbo-he 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 turbo-he 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.
How O3 protects you
O3 blocks turbo-he 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. turbo-he on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6xh4-h79w-9w2qRLMA-2026-05343

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks turbo-he-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