Malicious Code Detected in envoy1 Package - npm Vulnerability Alert

envoy1 Updated 12 Feb 2026

Summary

12/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-871: Malicious code in envoy1 (npm). Affects envoy1 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'envoy1' package, version 1.0.1, is a Node.js module available through npm that is designed for specific functionalities within JavaScript applications. However, it has been flagged as malicious due to its communication with a domain linked to harmful activities, raising significant security concerns for developers and users relying on this package.

Vulnerability Detail

The vulnerability in the 'envoy1' package stems from its malicious behavior, which includes unauthorized communication with a domain associated with malicious activities. This can lead to data breaches, unauthorized access to sensitive information, and potential exploitation of the systems using this package. The vulnerability was identified by the OpenSSF Package Analysis project, which highlighted the risks posed by this package version.

How To Fix

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

npm uninstall envoy1

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, consider using alternative packages that do not exhibit malicious behavior. You can search for similar packages on npm and evaluate their security status before integrating them into your project.

Conclusion

The 'envoy1' package has been flagged for malicious activity, which poses significant risks to applications that utilize it. Developers are urged to remove this package and seek alternatives to ensure the security of their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for envoy1 →

Share this vulnerability

FAQ

The 'envoy1' package is a Node.js module available on npm, used for specific functionalities in JavaScript applications.

'envoy1' is considered malicious because it communicates with a domain linked to harmful activities, posing security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you are using 'envoy1', you should uninstall it immediately and look for alternative packages that do not have known vulnerabilities.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall envoy1

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