Critical Malicious Code Vulnerability in e3tt87 Package

e3tt87 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19053: Malicious code in e3tt87 (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 e3tt87 package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and lightweight nature. However, this package has been found to contain malicious code, posing significant risks to applications that incorporate it.

Vulnerability Detail

The vulnerability in the e3tt87 package arises from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and has been confirmed by security researchers.

How To Fix

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

npm uninstall e3tt87

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 replacing the e3tt87 package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and remove any references to e3tt87.

Conclusion

The e3tt87 package contains a critical vulnerability due to malicious code, posing significant risks to applications. It is crucial to remove or update this package to safeguard your projects. Utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for e3tt87 →

Share this vulnerability

FAQ

The e3tt87 package is an npm library used in JavaScript applications, but it has been identified to contain malicious code.

The vulnerability was discovered by security researchers from Amazon Inspector, who identified the presence of malicious code in the package.

Using the e3tt87 package can lead to unauthorized access, data breaches, and other security issues within your application.

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

If immediate removal is not possible, consider implementing security measures to mitigate risks, such as restricting access to sensitive data and monitoring application behavior.

How To Fix

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

npm uninstall e3tt87

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