Critical Malicious Code Vulnerability in signals-embed Package

signals-embed Updated 19 Nov 2025

Summary

17/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190511: Malicious code in signals-embed (npm). Affected versions are not published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The signals-embed package is an npm library designed for embedding signals in web applications. It is commonly used for integrating various functionalities into JavaScript applications. However, this package has been found to contain malicious code that compromises the security of systems where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the signals-embed package. This code can lead to a complete compromise of any computer that has the package installed. It poses serious risks, including unauthorized access to sensitive information, such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code.

How To Fix

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

npm uninstall signals-embed

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, ensure that the signals-embed package is uninstalled from your system. You can do this by running the following command in your terminal: npm uninstall signals-embed. Additionally, monitor your system for any unusual activity and consider using security tools to scan for residual threats.

Conclusion

The signals-embed package has been identified as containing malicious code, posing significant security risks. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for signals-embed →

Share this vulnerability

FAQ

Immediately uninstall the signals-embed package and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check if your application is affected without any signup.

Keeping the signals-embed package can lead to unauthorized access to your system, data breaches, and potential control by malicious entities.

After removing the package, ensure to rotate all secrets and keys. Conduct a thorough security audit of your system to identify any remaining threats.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to their latest versions.

How To Fix

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

npm uninstall signals-embed

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