Which versions of signalk-poc-bug are malicious?

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

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

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

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

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

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

Malicious package

signalk-poc-bugnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1846

Immediate action

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

npm uninstall signalk-poc-bug

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c4b26530142d15002afe6db523fd2d7b5a5eab37f8a38e9dc1d0e7d8c9dc32ea

cf69e2f2bf99c9fcd93e12139a947e034130e9f90b30def5cf03d008c3f40330

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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