Which versions of @abb-americas/angular-components are malicious?

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

How do I remediate @abb-americas/angular-components if I installed it?

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

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

Yes — @abb-americas/angular-components is associated with the RLMA-2024-00000, RLUA-2024-05852, RLUA-2026-05786 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/angular-components across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @abb-americas/angular-components (version 1.0.0).

Malicious package

@abb-americas/angular-componentsnpm

Advisory published Jun 25, 2024Updated Sep 1, 2026

@abb-americas/angular-components is a confirmed malicious npm package (MAL-2024-1756) 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/angular-components (npm)

MAL-2024-1756

Immediate action

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

npm uninstall @abb-americas/angular-components

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

df097453e43c0eb7f99883612f0be1eb4cfcb76e15f553be676b25fdfe9df12f

73bedca88ed675a4df6d4928c84f5c44cbd62643fc1b6bd0d8f38d06e7bf3644

b39c13b14a664eb8ca28492c1df1f3e994b4a22385ee89bdfb4a0539e6546a36

991b326cfcd887440c5f4c63e2fc8e95a5cafd42c2554f2c79e97b8c279069fb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @abb-americas/angular-components (version 1.0.0).
If you installed it — respond
Remove @abb-americas/angular-components 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/angular-components 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/angular-components 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-00000RLUA-2024-05852RLUA-2026-05786

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @abb-americas/angular-components-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