Critical Malicious Code Vulnerability in eombfe Package

eombfe Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19691: Malicious code in eombfe (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 eombfe package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its recent discovery of malicious code poses significant security risks. Users of this package may unknowingly expose their applications to harmful operations due to this vulnerability.

Vulnerability Detail

The eombfe package has been identified to contain malicious code that can compromise the integrity of applications utilizing it. This vulnerability originated from the package's codebase, which was intentionally altered to include harmful scripts. The ramifications of this vulnerability can include unauthorized data access, data manipulation, and potential exploitation of the host system. Users are strongly advised to take immediate action to mitigate risks associated with this malicious code.

How To Fix

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

npm uninstall eombfe

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 eombfe package from their project until a secure version is confirmed. This can be done using the command: 'npm uninstall eombfe'. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The eombfe package has been found to contain malicious code, posing serious risks to applications that utilize it. Users are urged to update to the latest version or remove the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for eombfe →

Share this vulnerability

FAQ

The eombfe package is an npm library used for various functionalities in JavaScript applications, but its specific use cases may vary among developers.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground at Vulert Scanner, you can check if your application is affected without any signup.

Using the eombfe package can expose your application to malicious activities, including unauthorized access to data and potential exploitation of your system.

Yes, users are advised to update to the latest patched version of the eombfe package to eliminate the vulnerability.

If immediate updates are not possible, consider removing the eombfe package from your project as a temporary measure until a secure version is available.

How To Fix

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

npm uninstall eombfe

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