Malicious Code Detected in erafovnee Package - Immediate Action Required

erafovnee Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19758: Malicious code in erafovnee (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 erafovnee package is an npm library that serves various functionalities within JavaScript applications. It is designed to streamline certain processes, but its recent identification as containing malicious code raises significant concerns. Users of this package must be aware of its vulnerabilities to protect their applications from potential threats.

Vulnerability Detail

The erafovnee package has been found to contain malicious code, which poses a serious risk to any application utilizing it. This vulnerability originated from the package's codebase, which was compromised to include harmful scripts. The ramifications of this vulnerability can include unauthorized access to sensitive data, data corruption, or even complete system takeover. It is crucial for developers to understand the technical aspects of this vulnerability to mitigate risks effectively.

How To Fix

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

npm uninstall erafovnee

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 prevent the erafovnee package from being executed in your application by removing it from your package.json file and running npm install to update your dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the erafovnee package highlights the importance of vigilance in software dependencies. Developers must take immediate action to remove the affected package and consider alternatives to safeguard their applications. Utilizing tools like Vulert can further enhance security by providing real-time vulnerability alerts.

See every vulnerability recorded for erafovnee →

Share this vulnerability

FAQ

The erafovnee package is an npm library used in JavaScript applications for various functionalities, but it has recently been flagged for containing malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for vulnerabilities.

Immediately remove the erafovnee package from your project and replace it with a secure alternative. Ensure to update your dependencies accordingly.

Currently, there is no patched version available for the erafovnee package. It is recommended to remove it until a secure alternative is found.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.

How To Fix

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

npm uninstall erafovnee

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