Which versions of @abi-labs-frontend/standards are malicious?

The following npm versions of @abi-labs-frontend/standards are flagged malicious: 9.99.15. Treat any of these as compromised.

How do I remediate @abi-labs-frontend/standards if I installed it?

Remove @abi-labs-frontend/standards 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 @abi-labs-frontend/standards — how do I know if it already compromised me?

If @abi-labs-frontend/standards 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 @abi-labs-frontend/standards part of a known attack campaign?

Yes — @abi-labs-frontend/standards is associated with the RLMA-2026-01693, RLUA-2026-05790 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 @abi-labs-frontend/standards across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @abi-labs-frontend/standards (version 9.99.15).

Malicious package

@abi-labs-frontend/standardsnpm

Advisory published Mar 24, 2026Updated Sep 1, 2026

@abi-labs-frontend/standards is a confirmed malicious npm package (MAL-2026-2329) that executes malicious code on install (malicious version 9.99.15). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @abi-labs-frontend/standards (npm)

MAL-2026-2329

Immediate action

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

npm uninstall @abi-labs-frontend/standards

What this malware does

The package @abi-labs-frontend/standards was found to contain malicious code.

Malicious versions

1 flagged

9.99.15

Indicators of compromise (SHA-256)

8d91fb32cbc15015cc7ab17e9f318d1c2b14e711838b3c609ffc0d2a3b457f88

a60eba79d2fd49b58fb2a2073d2b7c87f66c1ad781bc1a6137962f9b5e772449

d3a2fae0ac1b421bbcdcdc9ed4ce7cab7f24a1c8454c4ad393607c56afded5c9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01693RLUA-2026-05790

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @abi-labs-frontend/standards-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