Malicious Code Injection in secure-old-deploy-resolve-encode Package
Summary
MAL-2025-189397: Malicious code in secure-old-deploy-resolve-encode (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 secure-old-deploy-resolve-encode package is part of the npm ecosystem, which is widely used for managing JavaScript packages. 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. It is designed to modify existing package configurations, making it susceptible to exploitation.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the secure-old-deploy-resolve-encode package. This payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious code continuously republishes these variants to pollute the npm registry, potentially leading to reputation damage for developers and compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall secure-old-deploy-resolve-encodeIf 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 remove the secure-old-deploy-resolve-encode package from your project by executing the command: 'npm uninstall secure-old-deploy-resolve-encode'. This will prevent any malicious activity associated with the package until a secure version is available.
Conclusion
The secure-old-deploy-resolve-encode package has been compromised with malicious code that alters package configurations and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects from potential threats.
See every vulnerability recorded for secure-old-deploy-resolve-encode →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the modification of your package.json file and the introduction of malicious packages into your project, compromising its integrity.
You should immediately update the package to the latest patched version or uninstall it to mitigate the risk.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
