Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

axis-abc-search-accountnpm

Malicious code in axis-abc-search-account (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3075
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall axis-abc-search-account

What this malware does

The package axis-abc-search-account 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 'axis-abc-search-account' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

3 flagged
1.0.099.99.99100.0.0

Indicators of compromise (SHA-256)

81afebda84bd1f98ca1353fc325952f9e3fa311c7ee0ff9c23ec04dfe9baca7a
940253e64eab64d76178b547ceb87731aad0dbba1ca1f988571af776564c891b
64a48b097520f1651fe0457ad413aefb48334b710b62db0705c0e58aeed0f409
772c1f10900731d554d913c7fc657431c6ba685e178b3e285933df4493a004e7
abd94d39ba6351d6c3a9871433ca84413686e8ea4fbbb0641a42ab56b8b21b33

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for axis-abc-search-account (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axis-abc-search-account across your stack and pipelines.

  2. If you installed it — respond

    Remove axis-abc-search-account 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 axis-abc-search-account 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.

  4. How O3 protects you

    O3 blocks axis-abc-search-account 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. axis-abc-search-account on npm has been identified as a malicious package (versions 1.0.0, 99.99.99, 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q53f-j5w8-x7vh

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks axis-abc-search-account-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.

axis-abc-search-account (npm) malicious package — MAL-2026-3075 | O3 Security