Which versions of oxnoxon are malicious?

The following npm versions of oxnoxon are flagged malicious: 10.0.7. Treat any of these as compromised.

How do I remediate oxnoxon if I installed it?

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

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

Yes — oxnoxon is associated with the GHSA-3qj6-c6x2-w2w6 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 oxnoxon 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 oxnoxon (version 10.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oxnoxon across your stack and pipelines.

Malicious package

oxnoxonnpm

Malicious code in oxnoxon (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-493

Immediate action

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

npm uninstall oxnoxon

What this malware does

The package oxnoxon 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 'oxnoxon' @ 10.0.7 (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

10.0.7

Indicators of compromise (SHA-256)

fe833d43cf24d7d5f3bd48f4c09ecee19c4237f49a87600d412abf96b63a6f7f

07667b579e49b5aa7dcc235c9e846cb1ea838af728878c44548d30a94b136dd3

dfafb8b040b2477ed33376b3c89b6854913025495027f4d32d6d8cd675ee84ec

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

Campaign

GHSA-3qj6-c6x2-w2w6

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks oxnoxon-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