Malicious Code Detected in @bhyolken/echotest Package - Security Alert

@bhyolken/echotest Updated 03 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192271: Malicious code in @bhyolken/echotest (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 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 @bhyolken/echotest package is a Node.js module available through npm, designed for testing echo functionality in applications. It is widely used by developers for its simplicity and ease of integration. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @bhyolken/echotest package. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The malicious nature of the code was identified by Amazon Inspector, which flagged the package for containing harmful elements that could lead to data breaches or system exploitation.

How To Fix

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

npm uninstall @bhyolken/echotest

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, consider removing the @bhyolken/echotest package from your project until a secure version is released. You can uninstall it using the command: npm uninstall @bhyolken/echotest.

Conclusion

The discovery of malicious code in the @bhyolken/echotest package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers should take immediate action to mitigate risks by updating or removing the affected package.

See every vulnerability recorded for @bhyolken/echotest →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access or data manipulation.

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

If immediate updates are not possible, consider removing the package from your project as a temporary measure.

The vulnerability was identified by Amazon Inspector, which flagged the @bhyolken/echotest package for containing malicious code.

While specific exploits have not been detailed, the presence of malicious code indicates a potential for various attacks on affected applications.

How To Fix

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

npm uninstall @bhyolken/echotest

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