Which versions of signalk-bug-poc are malicious?

The following npm versions of signalk-bug-poc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate signalk-bug-poc if I installed it?

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

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

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

Search your lockfiles and build artifacts for signalk-bug-poc (version 1.0.0).

Malicious package

signalk-bug-pocnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

signalk-bug-poc is a confirmed malicious npm package (MAL-2026-1845) 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 signalk-bug-poc (npm)

MAL-2026-1845

Immediate action

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

npm uninstall signalk-bug-poc

What this malware does

The package signalk-bug-poc was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e051738d03109e6ee26e7bf35e75adf623de576cbff91507ac4f8d9f4be08c62

b0adf060e6869ffe604897fcdb22f8c2d7b1b88465e935b0f2755767748ae363

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks signalk-bug-poc-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