Critical Malicious Code Vulnerability in eceqoq Package

eceqoq Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19113: Malicious code in eceqoq (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The eceqoq 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 identified to contain malicious code, posing a significant risk to applications that depend on it.

Vulnerability Detail

The vulnerability in the eceqoq package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code could potentially lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall eceqoq

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 eceqoq package with an alternative library that provides similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The eceqoq package has been identified as containing malicious code, posing a significant risk to applications that utilize it. It is essential to remove this package and monitor for updates or patches. Tools like Vulert can assist in identifying vulnerabilities in your project.

See every vulnerability recorded for eceqoq →

Share this vulnerability

FAQ

The eceqoq package is an npm library used in JavaScript applications for specific functionalities, but it has been found to contain malicious code.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

You should remove the eceqoq package from your project and look for a secure alternative. If a patched version is available, update to that version.

The vulnerability was discovered by Amazon Inspector, a security tool that helps identify vulnerabilities in software packages.

Using the eceqoq package can lead to unauthorized access, data breaches, and other harmful actions within your application due to the malicious code it contains.

How To Fix

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

npm uninstall eceqoq

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