Which versions of tether-base are malicious?

The following npm versions of tether-base are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate tether-base if I installed it?

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

If tether-base 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.

Is tether-base part of a known attack campaign?

Yes — tether-base is associated with the GHSA-gwg8-p6mg-cp7g 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-base across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tether-base (version 99.0.0).

Malicious package

tether-basenpm

Advisory published Apr 25, 2026Updated Aug 17, 2026

tether-base is a confirmed malicious npm package (MAL-2026-3033) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tether-base (npm)

MAL-2026-3033

Immediate action

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

npm uninstall tether-base

What this malware does

The package tether-base 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.

The OpenSSF Package Analysis project identified 'tether-base' @ 99.0.0 (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

1 flagged

99.0.0

Indicators of compromise (SHA-256)

88b507927542b8b7858e8bcd5d8890f261e4db310240cb16df8c3da133df5be4

f3a15feaa501454125206345e0e802667759555738db7b1a1ee9ad5dc6b0098a

c4f8b53059155a1600bd55819f476e0fd647a42bcacb4c5d556208a730983007

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tether-base (version 99.0.0).
If you installed it — respond
Remove tether-base 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-base 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. tether-base on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gwg8-p6mg-cp7g

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks tether-base-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