Malicious Code Injection in buffer-materialize-config-subscription Package
Summary
MAL-2025-140161: Malicious code in buffer-materialize-config-subscription (npm). Affected versions are not published. 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 buffer-materialize-config-subscription package is part of the npm ecosystem, typically used for managing configuration subscriptions in applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior compromises the integrity of the npm registry and poses a risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the buffer-materialize-config-subscription package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which are often themed around Indonesian culture. The malicious code continuously republishes these variants, polluting the npm registry and potentially leading to security risks for developers who rely on this package. The impact of this vulnerability includes the risk of using compromised packages, which can lead to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall buffer-materialize-config-subscriptionIf 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 buffer-materialize-config-subscription package from your project until a secure version is released. You can do this by running: npm uninstall buffer-materialize-config-subscription. Additionally, monitor your package-lock.json file for any dependencies that may have been affected by this vulnerability.
Conclusion
The buffer-materialize-config-subscription package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to take immediate action by updating or removing the package to mitigate potential security risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for buffer-materialize-config-subscription →
FAQ
It is an npm package used for managing configuration subscriptions in applications, but it has been compromised with malicious code.
The malicious code modifies your package.json file and can lead to the installation of compromised packages, increasing security risks.
You should uninstall the package immediately and monitor your application for any unusual behavior or vulnerabilities.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.
Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and review package sources before installation.
