Critical Malicious Code Vulnerability in 02-echo Package

02-echo Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191025: Malicious code in 02-echo (npm). Affects 02-echo versions 0.0.7. 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 02-echo package is a Node.js module available through npm, designed for echoing messages in applications. It is often used in various projects for its simplicity and ease of integration. However, this package has been found to contain malicious code that compromises the security of any system where it is installed, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the 02-echo package, identified as GHSA-q2q8-5wg4-g6jq. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications include potential data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as compromised, as the malicious code may persist even after removal of the package.

How To Fix

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

npm uninstall 02-echo

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 the system. Users should ensure that they have backups of their data and configurations before proceeding with the removal.

Conclusion

The discovery of malicious code in the 02-echo package poses a serious threat 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 for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for 02-echo →

Share this vulnerability

FAQ

Immediately remove the 02-echo package and rotate any secrets or keys stored on the affected system.

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.

While removing the package is necessary, it is crucial to rotate all sensitive information and keys, as the malicious code may have already compromised your system.

Failing to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.

Not necessarily. While removing the package is essential, there is no guarantee that all malicious software installed as a result of the package will be removed.

How To Fix

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

npm uninstall 02-echo

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