Critical Malicious Code Vulnerability in @daffadeveloper/signal-node Package

@daffadeveloper/signal-node Updated 19 Jan 2026

Summary

19/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-330: Malicious code in @daffadeveloper/signal-node (npm). Affects @daffadeveloper/signal-node versions 1.0.1. 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 @daffadeveloper/signal-node package is an npm library designed for signal processing in Node.js applications. It provides developers with tools to implement various signal-related functionalities. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @daffadeveloper/signal-node package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged by the GHSA (GitHub Security Advisory) for containing malware. Users are advised to treat any system with this package as fully compromised, as the malicious code may persist even after the package is removed.

How To Fix

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

npm uninstall @daffadeveloper/signal-node

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

There are no effective workarounds for this vulnerability other than removing the package and securing your system. It is essential to ensure that all sensitive information is rotated and that the system is monitored for any unusual activity.

Conclusion

The @daffadeveloper/signal-node package has been identified as containing malicious code, posing a severe risk to any system where it is installed. Immediate action is required to remove the package and secure sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for @daffadeveloper/signal-node →

Share this vulnerability

FAQ

You should immediately remove the package and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

The only mitigation is to remove the package and secure your system. There are no effective workarounds.

Failure to address this vulnerability can lead to unauthorized access to sensitive information and full compromise of your system.

While removing the package is essential, it does not guarantee complete security. You should monitor your system for any signs of compromise.

How To Fix

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

npm uninstall @daffadeveloper/signal-node

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