Malicious Code Detected in npm Package eamcet - MAL-2025-19080

eamcet Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19080: Malicious code in eamcet (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 npm package 'eamcet' is designed for specific functionalities within the JavaScript ecosystem, often utilized for various web development tasks. However, it has been identified to contain malicious code, posing significant risks to applications that depend on it. This vulnerability can lead to unauthorized access or manipulation of data, making it critical for developers to be aware of its implications.

Vulnerability Detail

The vulnerability in the 'eamcet' package originates from the inclusion of malicious code that can compromise the security of applications using it. This code can potentially allow attackers to execute unauthorized actions, leading to data breaches or system integrity issues. The vulnerability is categorized as a SEMVER issue, meaning it affects all versions starting from the initial release (version 0).

How To Fix

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

npm uninstall eamcet

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 can avoid using the 'eamcet' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement security measures in your application to monitor for any suspicious activity.

Conclusion

The discovery of malicious code in the 'eamcet' npm package highlights the importance of vigilance in managing open-source dependencies. Developers are encouraged to remove the affected package and seek alternatives while utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for eamcet →

Share this vulnerability

FAQ

The 'eamcet' package is an npm package used in JavaScript development, but it has been found to contain malicious code.

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

You should remove the 'eamcet' package from your project and look for alternatives. If a patched version is released, update to that version.

Using a malicious package can lead to unauthorized access, data breaches, and compromise the integrity of your application.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall eamcet

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