Critical Malicious Code Vulnerability in epc-node-web-client Package

epc-node-web-client Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6926: Malicious code in epc-node-web-client (npm). Affects epc-node-web-client versions >= 10.0.0. 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 epc-node-web-client package is a Node.js client designed for interacting with EPC (Electronic Product Code) systems. It facilitates communication between applications and EPC services, enabling functionalities such as data retrieval and submission. However, this package has been identified to communicate with a domain linked to malicious activities, posing significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability stems from the package's communication with a domain associated with malicious activities. This could lead to unauthorized data access, data exfiltration, or the execution of harmful code within the user's environment. The issue was introduced in version 10.0.0 and has been classified as a serious security concern due to its potential impact on user data and application integrity.

How To Fix

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

npm uninstall epc-node-web-client

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 removing the epc-node-web-client package from your project until a secure version is released. You can do this by executing: npm uninstall epc-node-web-client. Additionally, review your application for any dependencies that may rely on this package.

Conclusion

The epc-node-web-client package has a critical vulnerability that allows communication with a malicious domain, posing significant risks to applications. It is crucial to update or remove the package to safeguard your application from potential threats. Utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for epc-node-web-client →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain associated with malicious activities, which can compromise application security.

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

If immediate updates are not feasible, consider removing the package as a temporary measure to mitigate risks.

While specific exploits have not been detailed, the nature of the vulnerability suggests potential for data breaches and unauthorized access.

You can find more information on the package's GitHub repository or its npm page, which provides documentation and updates.

How To Fix

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

npm uninstall epc-node-web-client

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