Malicious Code Detected in ericcui Package - Security Alert

ericcui Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19766: Malicious code in ericcui (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 ericcui package is a Node.js library commonly used in various applications for its functionality and ease of integration. However, it has been identified as containing malicious code, posing a significant risk to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and other security issues.

Vulnerability Detail

The vulnerability in the ericcui package stems from the inclusion of malicious code that can execute harmful actions within the user's environment. This code was introduced in version 0 and can compromise the integrity of applications that rely on this package. Users may experience data loss, unauthorized data access, or system instability as a result of this vulnerability.

How To Fix

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

npm uninstall ericcui

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 consider using alternative packages that provide similar functionality without the associated risks. It is advisable to conduct a thorough review of dependencies to ensure no other vulnerable packages are present.

Conclusion

The discovery of malicious code in the ericcui package poses a serious threat to users and their applications. Immediate action is required to remove the package and mitigate potential risks. Staying informed about vulnerabilities and using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for ericcui →

Share this vulnerability

FAQ

The ericcui package is a Node.js library used in various applications for specific functionalities. However, it has been flagged for containing malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is impacted.

The risks include unauthorized access to sensitive data, potential data breaches, and overall instability of applications using the compromised package.

While the best course of action is to remove the package, you can explore alternative packages that offer similar functionalities without the security risks.

Regularly check for updates on your dependencies and consider using tools like Vulert to monitor vulnerabilities in real-time.

How To Fix

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

npm uninstall ericcui

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