Which versions of libjs-cqs are malicious?

The following npm versions of libjs-cqs are flagged malicious: 90.9.0. Treat any of these as compromised.

How do I remediate libjs-cqs if I installed it?

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

If libjs-cqs 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 libjs-cqs part of a known attack campaign?

Yes — libjs-cqs is associated with the RLMA-2026-01400 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 libjs-cqs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libjs-cqs (version 90.9.0).

Malicious package

libjs-cqsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

libjs-cqs is a confirmed malicious npm package (MAL-2026-1770) that executes malicious code on install (malicious version 90.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libjs-cqs (npm)

MAL-2026-1770

Immediate action

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

npm uninstall libjs-cqs

What this malware does

The package libjs-cqs was found to contain malicious code.

Malicious versions

1 flagged

90.9.0

Indicators of compromise (SHA-256)

604d09fdc85fe0eac0452b09fb9af706422368a9dad6a70d3147350c2394b5a0

aed1ca0473a0b4d14330082b90a8fa15e7f1dfc671361ad4ef8c2dac38b130b0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for libjs-cqs (version 90.9.0).
If you installed it — respond
Remove libjs-cqs 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 libjs-cqs 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. libjs-cqs on npm has been identified as a malicious package (version 90.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01400

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks libjs-cqs-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