Which versions of loadshh are malicious?

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

How do I remediate loadshh if I installed it?

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

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

Yes — loadshh is associated with the RLMA-2026-01783 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 loadshh across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for loadshh (version 1.0.0).

Malicious package

loadshhnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

loadshh is a confirmed malicious npm package (MAL-2026-2369) 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 loadshh (npm)

MAL-2026-2369

Immediate action

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

npm uninstall loadshh

What this malware does

The package loadshh was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

659b7839d263e00039c4d6ef918c9edcadcc18ea3730742736c35f0e40def7ee

c1d004f6eea15c013bd06ee8a4dd18dff1443aacb9ced1b110a7d05f59bc5438

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for loadshh (version 1.0.0).
If you installed it — respond
Remove loadshh 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 loadshh 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. loadshh 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-2026-01783

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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