Which versions of aabquery are malicious?

The following npm versions of aabquery are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate aabquery if I installed it?

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.

I already installed aabquery — how do I know if it already compromised me?

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

Is aabquery part of a known attack campaign?

Yes — aabquery is associated with the RLMA-2024-00290, RLUA-2024-06097, RLUA-2026-10670 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 aabquery across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aabquery (2 malicious versions).

Malicious package

aabquerynpm

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Find it
Search your lockfiles and build artifacts for aabquery (2 malicious versions).
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.
Did it already run?
If aabquery 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. 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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database