Malicious Code Injection in deliberate_dolphin_z3n: A Threat to npm Packages
Summary
MAL-2025-93956: Malicious code in deliberate_dolphin_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 package 'deliberate_dolphin_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers and their projects.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'deliberate_dolphin_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The malicious payload can lead to unauthorized access, reputation damage, and potential exploitation of affected systems, as it allows the package to continuously republish variants without user consent.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall deliberate_dolphin_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 'deliberate_dolphin_z3n' package from your project by executing: 'npm uninstall deliberate_dolphin_z3n'. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'deliberate_dolphin_z3n' package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for deliberate_dolphin_z3n →
FAQ
It is an npm package that is part of a campaign to inflate developer reputation scores by publishing numerous derivative packages.
The malicious code can modify your package.json, remove private flags, and republish variants, leading to potential security risks and reputation damage.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If an update is not available, consider removing the package entirely and monitoring your project for any unusual behavior.
Yes, Vulert monitors your package-lock.json for open-source vulnerabilities in real-time, helping you stay informed about potential threats.
