Which versions of tachyon-spade-reporter are malicious?

Every published version of tachyon-spade-reporter on npm is considered malicious. Remove the package entirely.

How do I remediate tachyon-spade-reporter if I installed it?

tachyon-spade-reporter is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tachyon-spade-reporter — how do I know if it already compromised me?

If tachyon-spade-reporter 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 tachyon-spade-reporter part of a known attack campaign?

Yes — tachyon-spade-reporter is associated with the GHSA-5w2f-897r-j622 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 tachyon-spade-reporter 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 tachyon-spade-reporter (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tachyon-spade-reporter across your stack and pipelines.

Malicious package

tachyon-spade-reporternpm

Malicious code in tachyon-spade-reporter (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1386

Immediate action

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

npm uninstall tachyon-spade-reporter

What this malware does

The package exfiltrates system data to remote server

The package tachyon-spade-reporter 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)

1115b7a469055bf285d16f0331dad3e3175d072deb56cc5d4be49d2270c650b0

80ad134ce018cc5d3d53f7bcb89de68046aacd2438d13bd6fb93875be5380223

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tachyon-spade-reporter (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tachyon-spade-reporter across your stack and pipelines.
If you installed it — respond
tachyon-spade-reporter is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tachyon-spade-reporter 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 tachyon-spade-reporter 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. tachyon-spade-reporter 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-5w2f-897r-j622

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks tachyon-spade-reporter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring