Malicious Code Detected in eetesting Package - Security Alert

eetesting Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19237: Malicious code in eetesting (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 eetesting package is an npm module designed for testing purposes within JavaScript applications. It provides various functionalities that assist developers in creating and executing tests efficiently. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the eetesting package originates from the inclusion of malicious code that can compromise the integrity of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions that can affect both developers and end-users. The malicious nature of this code makes it imperative for users to take immediate action to safeguard their applications.

How To Fix

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

npm uninstall eetesting

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, you may consider removing the eetesting package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall eetesting'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the eetesting package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are urged to take immediate action by updating or uninstalling the affected package to mitigate security risks.

See every vulnerability recorded for eetesting →

Share this vulnerability

FAQ

The eetesting package is an npm module used for testing JavaScript applications, providing various testing functionalities.

The malicious code found in eetesting can lead to unauthorized access and potential data breaches in applications that use this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Yes, you should update the eetesting package to the latest version to ensure that the malicious code is removed.

If you cannot update the package right away, consider uninstalling it as a temporary measure to protect your application from potential threats.

How To Fix

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

npm uninstall eetesting

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