Which versions of tahoe-tap are malicious?

Every published version of tahoe-tap on npm is considered malicious. Remove the package entirely.

How do I remediate tahoe-tap if I installed it?

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

If tahoe-tap 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 tahoe-tap part of a known attack campaign?

Yes — tahoe-tap is associated with the GHSA-777p-fm5x-p7rg 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 tahoe-tap 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 tahoe-tap (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tahoe-tap across your stack and pipelines.

Malicious package

tahoe-tapnpm

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

MAL-2026-1387

Immediate action

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

npm uninstall tahoe-tap

What this malware does

Malicious package detected. Executes code during installation via preinstall script in package.json and has only one version published.

The package tahoe-tap 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c5105b324bf7dc41e9bce318b47bb5bea6e3193f688daa6ac3b153ae9f226fbe

deec4b3e879632ae9819b52e88ae689725b1af688aecd541e498d2bac084f848

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 tahoe-tap (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tahoe-tap across your stack and pipelines.
If you installed it — respond
Remove tahoe-tap 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 tahoe-tap 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 tahoe-tap 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. tahoe-tap on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-777p-fm5x-p7rg

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks tahoe-tap-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