Malicious Code Vulnerability in signalk-poc-bug Package

signalk-poc-bug Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1846: Malicious code in signalk-poc-bug (npm). Affects signalk-poc-bug 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The signalk-poc-bug package is an npm module designed for specific functionalities within the Signal K protocol, which is used for marine data communication. This package, like many others in the npm ecosystem, can be susceptible to malicious code injections, which can compromise the integrity and security of applications relying on it.

Vulnerability Detail

The vulnerability identified as MAL-2026-1846 involves the presence of malicious code within the signalk-poc-bug package. This issue originates from a compromised version of the package (version 1.0.0) that was published to the npm registry. The ramifications of this vulnerability can include unauthorized access to sensitive data, execution of arbitrary code, and potential system compromise. It is crucial for users of this package to be aware of the risks associated with using this version.

How To Fix

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

npm uninstall signalk-poc-bug

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 temporary measure, users can avoid using the compromised version of the signalk-poc-bug package by removing it from their project. This can be done using the command: 'npm uninstall signalk-poc-bug'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The signalk-poc-bug package has been identified with a serious vulnerability due to malicious code. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for signalk-poc-bug →

Share this vulnerability

FAQ

The signalk-poc-bug package is an npm module used for functionalities related to the Signal K protocol, primarily in marine data communication.

You can check if your application is affected by this vulnerability using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

If you are using version 1.0.0 of the signalk-poc-bug package, it is recommended to uninstall it and update to a secure version as soon as possible.

Using a compromised package can lead to unauthorized access to sensitive data, execution of malicious code, and overall system compromise.

Currently, there is no specific patched version mentioned for the signalk-poc-bug package. Users should monitor the npm registry for updates and security patches.

How To Fix

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

npm uninstall signalk-poc-bug

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