Which versions of apexomni are malicious?

The following npm versions of apexomni are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate apexomni if I installed it?

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

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

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

Malicious package

apexomninpm

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

MAL-2026-3233

Immediate action

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

npm uninstall apexomni

What this malware does

The package apexomni 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 'apexomni' @ 99.99.99 (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.99.99

Indicators of compromise (SHA-256)

84e05c582c9d898b04787eb59f54ae1ea01d506ec94ec86029e2bffc1cd7357c

a53c153f68abdc118a92f4c3a13c2ad21e0d098bdf5e7cf57e679e467b226c06

8ec8450f87a6c99576d96e1c59179c61ef89603915c8d003af0f5f6992348092

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

Campaign

GHSA-m6v2-w5cf-f85x

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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