NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

apexomninpm

Advisory published Updated

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

Malicious code in apexomni (npm)

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
  1. Find it

    Search your lockfiles and build artifacts for apexomni (version 99.99.99).

  2. 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.

  3. Did it already run?

    If apexomni 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. 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

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.

Explore

apexomni (npm) malicious package — MAL-2026-3233 | O3 Security