Critical Malicious Code Vulnerability in echo-avy-project (npm)

echo-avy-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19119: Malicious code in echo-avy-project (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 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 echo-avy-project is an npm package designed for developers to facilitate specific functionalities within their applications. It is widely used in various projects due to its ease of integration and utility. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the echo-avy-project package. This code can lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address it promptly.

How To Fix

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

npm uninstall echo-avy-project

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 workaround, users can remove the echo-avy-project package from their project until a secure version is released. This can be done using the command: npm uninstall echo-avy-project.

Conclusion

The echo-avy-project package has been identified as containing malicious code, posing a serious threat to users. Immediate action is required to update or remove the package to safeguard applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for echo-avy-project →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially compromising user data and application integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.

Yes, you can temporarily uninstall the echo-avy-project package until a secure version is released.

It is crucial to remove the package immediately and monitor your application for any unusual activity. Consider conducting a security audit.

Detailed information can be found on the GitHub repository of the malicious package, which provides insights into the vulnerability and its implications.

How To Fix

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

npm uninstall echo-avy-project

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