Malicious Code Vulnerability in signalk-bug-poc Package

signalk-bug-poc Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1845: Malicious code in signalk-bug-poc (npm). Affects signalk-bug-poc versions 1.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The signalk-bug-poc package is an npm library designed for testing and demonstration purposes within the Signal K ecosystem. It is used by developers to simulate various scenarios in applications that utilize the Signal K protocol. However, this package has been identified to contain malicious code that poses a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the signalk-bug-poc package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The vulnerability was reported by ReversingLabs and affects version 1.0.0 of the package. Users are advised to be cautious and ensure they are not using this compromised version in their projects.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall signalk-bug-poc

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, users can replace the signalk-bug-poc package with alternative libraries that provide similar functionality without the associated risks. It is crucial to review the dependencies of your project and ensure that no malicious packages are included.

Conclusion

The signalk-bug-poc package has been identified to contain malicious code that poses a serious security risk. Users should take immediate action to remove this package from their projects and seek alternatives. Monitoring tools like Vulert can help ensure that your applications remain secure from such vulnerabilities.

See every vulnerability recorded for signalk-bug-poc →

Share this vulnerability

FAQ

The signalk-bug-poc package is an npm library used for testing and demonstration within the Signal K ecosystem.

The vulnerability involves malicious code that can compromise the security of applications using the package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

You should remove the signalk-bug-poc package from your project immediately and look for alternative libraries.

Currently, there is no patched version available for the signalk-bug-poc package, so it is advised to avoid using it.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall signalk-bug-poc

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback