Which versions of tether-dev-docs are malicious?

Every published version of tether-dev-docs on npm is considered malicious. Remove the package entirely.

How do I remediate tether-dev-docs if I installed it?

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

If tether-dev-docs 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 tether-dev-docs part of a known attack campaign?

Yes — tether-dev-docs is associated with the GHSA-6c8j-272h-r6h7 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 tether-dev-docs 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 tether-dev-docs (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tether-dev-docs across your stack and pipelines.

Malicious package

tether-dev-docsnpm

Malicious code in tether-dev-docs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1258

Immediate action

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

npm uninstall tether-dev-docs

What this malware does

The package tether-dev-docs 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)

57a6db50523e4b656bdec519331a0443d43f1f9ae2dd91e5e1a1ee5ab6cc5ed3

b0d07b28a3afe4c020244ad7d5415342f3d62c4436107a5d764307d102b193ef

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 tether-dev-docs (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tether-dev-docs across your stack and pipelines.
If you installed it — respond
Remove tether-dev-docs 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 tether-dev-docs 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 tether-dev-docs 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. tether-dev-docs 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-6c8j-272h-r6h7

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tether-dev-docs-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