Which versions of shiphero-dashboard are malicious?

The following npm versions of shiphero-dashboard are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate shiphero-dashboard if I installed it?

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

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

Yes — shiphero-dashboard is associated with the RLMA-2026-05313, RLUA-2026-06486 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 shiphero-dashboard across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for shiphero-dashboard (version 1.1.0).

Malicious package

shiphero-dashboardnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

shiphero-dashboard is a confirmed malicious npm package (MAL-2026-7419) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shiphero-dashboard (npm)

MAL-2026-7419

Immediate action

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

npm uninstall shiphero-dashboard

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

22af54b4c94fa90c57f7f02940195024d8afe4c1667ab056c51795cc5706f013

88981aff96ee33791bedc6e353bfc27b6fc62e2295bbb59dc44b97a78af95331

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05313RLUA-2026-06486

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks shiphero-dashboard-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