Which versions of suit-base are malicious?

The following npm versions of suit-base are flagged malicious: 45.0.0. Treat any of these as compromised.

How do I remediate suit-base if I installed it?

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

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

Yes — suit-base is associated with the RLMA-2026-05326, RLUA-2026-06514 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 suit-base across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for suit-base (version 45.0.0).

Malicious package

suit-basenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

suit-base is a confirmed malicious npm package (MAL-2026-7426) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in suit-base (npm)

MAL-2026-7426

Immediate action

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

npm uninstall suit-base

Malicious versions

1 flagged

45.0.0

Indicators of compromise (SHA-256)

56d97e74de439188eaf0c8575a4552c299b0de9c44df35ad32a4e3030774865b

44a10417925006c6acb8b5db371402fa324ade7d27a635f37f7285283b11c54e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05326RLUA-2026-06514

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks suit-base-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