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

axis-abc-search-addressnpm

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

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

What this malware does

The package axis-abc-search-address 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-address' @ 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)

5174d7363bb92d92512d5ade27465253ab07a0eba377301e9dd1defc06e8a05a
12745094744214b57071e8ace8ee7d5ee3f9be6e7d29d338bb4bbd01842f2705
7cf11f479f198bd2d738c695692678985a9d3e3c7fc415c38393a8ffc95d7ea7
f43101340b146c37405bb884b8921beb23781e06dd7ff11cadfa675c179feac5
0efb8626ea4c2a7dc4a9372450389d99bd8f62a28854904224811fd94a91e42d

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-address (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-address across your stack and pipelines.

  2. If you installed it — respond

    Remove axis-abc-search-address 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-address 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-address 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-address 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-r78p-pprh-8hvp

References

Credits

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

Detect & block this

O3 blocks axis-abc-search-address-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-address (npm) malicious package — MAL-2026-3076 | O3 Security