Which versions of aabquerys are malicious?

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

How do I remediate aabquerys if I installed it?

Remove aabquerys 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 aabquerys — how do I know if it already compromised me?

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

Is aabquerys part of a known attack campaign?

Yes — aabquerys is associated with the RLMA-2024-00291, RLUA-2024-06098, RLUA-2026-10671 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 aabquerys across my projects, lockfiles, and CI pipelines?

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

Malicious package

aabquerysnpm

aabquerys is a confirmed malicious npm package (MAL-2024-1711) 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 aabquerys (npm)

MAL-2024-1711

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall aabquerys

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

bfe5c42d3ef30e6646f3fa3f1d051e99556bde034e42e5b15c7c3e3287c7f06d

f4da6490e89dfee01ca9b58194d626714fb1d69471966310c54a936a557847ed

4ecfd22dc54f800fe2e4b974e66c5a12914be5c9f48df9d29372c654cf94296c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aabquerys (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aabquerys across your stack and pipelines.
If you installed it — respond
Remove aabquerys 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 aabquerys 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.
How O3 protects you
O3 blocks aabquerys 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. aabquerys 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-00291RLUA-2024-06098RLUA-2026-10671

References

Credits

ReversingLabs · finder

Detect & block this

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