Which versions of abcvbs are malicious?

The following npm versions of abcvbs are flagged malicious: 3.2.1. Treat any of these as compromised.

How do I remediate abcvbs if I installed it?

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

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

Yes — abcvbs is associated with the RLMA-2024-00294, RLUA-2024-06101, RLUA-2026-10676 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 abcvbs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for abcvbs (version 3.2.1).

Malicious package

abcvbsnpm

Advisory published Jun 25, 2024Updated Sep 24, 2026

abcvbs is a confirmed malicious npm package (MAL-2024-1714) that executes malicious code on install (malicious version 3.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abcvbs (npm)

MAL-2024-1714

Immediate action

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

npm uninstall abcvbs

Malicious versions

1 flagged

3.2.1

Indicators of compromise (SHA-256)

70e5eb5292426e90ecffbba72ccbb6d4879ad1dd8c8de78dab361937125c6e3c

bae92aa2184b3e790a0ed1bbea47ff84ec77951e790f0f3dec4e92e417beb417

111517041ac8eae284c58312df697dd7b6ccf05298f1c04a614d20771e49c41e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-00294RLUA-2024-06101RLUA-2026-10676

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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