Malicious Code Vulnerability in @coopeuch/config Package
Summary
MAL-2026-17762: Malicious code in @coopeuch/config (npm). Affects @coopeuch/config versions 1.999.999. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @coopeuch/config package is an npm package designed for configuration management in JavaScript applications. It is intended to streamline the process of managing application settings and configurations. However, a severe vulnerability has been identified in version 1.999.999, which allows for the execution of malicious code during the installation process, potentially compromising user data and internal infrastructure.
Vulnerability Detail
The vulnerability originates from a malicious implementation in the package's post-installation script (postinstall.js). When the package is installed, it automatically collects sensitive information such as hostname, username, user IDs, and network interface addresses, and sends this data to a hardcoded external server. This behavior occurs without user consent, posing significant risks to organizations that may inadvertently install this package, as it can lead to data leaks and exposure of internal project identifiers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @coopeuch/configIf 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 execution of scripts during installation by using the following command: npm install @coopeuch/config --ignore-scripts. This will stop the malicious post-install script from running, but it is advisable to remove the package entirely until a safe version is available.
Conclusion
The @coopeuch/config package has a critical vulnerability that allows for the execution of malicious code during installation, leading to potential data leaks and security risks. It is essential to avoid using the affected version and to monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.
See every vulnerability recorded for @coopeuch/config →
FAQ
The main issue is that it contains malicious code that collects sensitive information from the host system during installation.
You can use Vulert, which monitors open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check your application without signing up.
If you have installed the affected version, it is recommended to uninstall it immediately and check for any updates or patches.
Yes, you can use the command 'npm install @coopeuch/config --ignore-scripts' to prevent the execution of any scripts during the installation.
The consequences include unauthorized data collection, exposure of internal infrastructure details, and potential security breaches within the organization.
