Which versions of abb-americas are malicious?

The following npm versions of abb-americas are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate abb-americas if I installed it?

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

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

Yes — abb-americas is associated with the RLMA-2024-00292, RLUA-2024-06099, RLUA-2026-10674 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 abb-americas across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for abb-americas (version 1.0.0).

Malicious package

abb-americasnpm

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in abb-americas (npm)

MAL-2024-1712

Immediate action

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

npm uninstall abb-americas

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2ca5b7483a4ef1302a52163de2d8643e7ab6272c3f6a6bcb6479809ad27b86b0

2385e4cb4479251157d14b1d493c55d9cce7a393bf2204360b472c165b8a94dc

f815faa318503663614e2f8ebb62f6d5fbd289059b27b093cc141c30b9e472a0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-00292RLUA-2024-06099RLUA-2026-10674

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks abb-americas-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