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

aabquerynpm

aabquery is a confirmed malicious npm package (MAL-2024-1710) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aabquery (npm)

MAL-2024-1710
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall aabquery

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

d920886bf4ca4a5d8e3b487097ddeda382d5f743070ff2357648e961c96a9ed4
cb4eff5ab49fa48d419ad58986a89fc0de071ffd3f8508dea23ca747b4d8a755
1ccf6f2326af186ed131cfe914f2340742d0eae837f7764d6b917ff410372710

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 aabquery (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aabquery across your stack and pipelines.

  2. If you installed it — respond

    Remove aabquery 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 aabquery 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 aabquery 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. aabquery on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00290RLUA-2024-06097RLUA-2026-10670

References

Credits

  • ReversingLabs · finder

Detect & block this

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

aabquery (npm) malicious package — MAL-2024-1710 | O3 Security