Malicious Code Injection in corresponding_newt_z3n Package
Summary
MAL-2025-101022: Malicious code in corresponding_newt_z3n (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 corresponding_newt_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is often included in projects to manage dependencies and facilitate package management. 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 poses a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the corresponding_newt_z3n package stems from its involvement in a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious code is designed to exploit the npm ecosystem, making it crucial for developers to be aware of its implications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall corresponding_newt_z3nIf 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 corresponding_newt_z3n package from your project by executing the command: 'npm uninstall corresponding_newt_z3n'. This will prevent any malicious code from executing while you assess alternative packages.
Conclusion
The corresponding_newt_z3n package has been identified as containing malicious code that can compromise the security of applications. It is essential for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.
See every vulnerability recorded for corresponding_newt_z3n →
FAQ
The corresponding_newt_z3n package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry and compromise the security of applications that depend on the affected package.
You should update the package to a patched version or uninstall it to prevent potential security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
