Which versions of @taxmoninor/taxmon are malicious?

The following npm versions of @taxmoninor/taxmon are flagged malicious: 99.0.7. Treat any of these as compromised.

How do I remediate @taxmoninor/taxmon if I installed it?

Remove @taxmoninor/taxmon 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 @taxmoninor/taxmon — how do I know if it already compromised me?

If @taxmoninor/taxmon 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 @taxmoninor/taxmon part of a known attack campaign?

Yes — @taxmoninor/taxmon is associated with the GHSA-qpg7-5r8v-6h76 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 @taxmoninor/taxmon 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 @taxmoninor/taxmon (version 99.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @taxmoninor/taxmon across your stack and pipelines.

Malicious package

@taxmoninor/taxmonnpm

Malicious code in @taxmoninor/taxmon (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3121

Immediate action

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

npm uninstall @taxmoninor/taxmon

What this malware does

The package @taxmoninor/taxmon 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 '@taxmoninor/taxmon' @ 99.0.7 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.0.7

Indicators of compromise (SHA-256)

26a2ba1d60a7354a9d1329829ce0146a850ad9f676df6d30385a1a8cf6121114

42f9358f8af80b7021c6d4bb86f10796de5ad8ef2ec941d0057954b9e6a18355

dfbd1011e5972e199d893ef1d4bc0c981cb0df2e84fbe1bcdb15f03e42bab66e

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

Campaign

GHSA-qpg7-5r8v-6h76

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @taxmoninor/taxmon-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