Malicious Code Injection in parallel_dingo-biggestdev: A Threat to npm Users
Summary
MAL-2025-106900: Malicious code in parallel_dingo-biggestdev (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 package 'parallel_dingo-biggestdev' is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'parallel_dingo-biggestdev' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks and dependency issues.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parallel_dingo-biggestdevIf 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 'parallel_dingo-biggestdev' package from your project by executing the command: 'npm uninstall parallel_dingo-biggestdev'. This will prevent any malicious code from executing while you assess alternative packages or wait for a patched version.
Conclusion
The 'parallel_dingo-biggestdev' package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is essential for developers to take immediate action by removing the package and monitoring their projects for any potential impacts. Utilizing tools like Vulert can help in maintaining the security of your software.
See every vulnerability recorded for parallel_dingo-biggestdev →
FAQ
'parallel_dingo-biggestdev' is an npm package that has been identified as malicious, designed to manipulate package metadata for fraudulent purposes.
The vulnerability can lead to the injection of malicious code, compromising your project's security and potentially affecting its functionality.
If you have installed 'parallel_dingo-biggestdev', you should uninstall it immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with security advisories.
