Malicious Code Injection in certain_shark_z3n Package - npm Vulnerability
Summary
MAL-2025-100314: Malicious code in certain_shark_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 certain_shark_z3n package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The functionality of this package is compromised due to its malicious intent, making it a significant risk for developers using it.
Vulnerability Detail
The vulnerability originates from the certain_shark_z3n package, which includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. Developers using this package may unknowingly contribute to the spread of malicious code, affecting the security of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall certain_shark_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 workaround, you can temporarily avoid using the certain_shark_z3n package by not including it in your project dependencies. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time, ensuring that your application remains secure.
Conclusion
The certain_shark_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. Developers should take immediate action to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.
See every vulnerability recorded for certain_shark_z3n →
FAQ
The certain_shark_z3n package is part of a malicious campaign that floods the npm registry with packages designed to inflate developer reputation scores.
The vulnerability can lead to the modification of your package.json file, potentially compromising the integrity of your application and exposing it to further risks.
You should uninstall the certain_shark_z3n package immediately and review your project for any dependencies that may rely on it.
Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Regularly monitor your dependencies using tools like Vulert, and stay updated on security advisories related to the packages you use.
