Malicious Code Detected in regulatory_shark_z3n: A Threat to npm Users
Summary
MAL-2025-107832: Malicious code in regulatory_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 package regulatory_shark_z3n is part of a broader campaign that exploits npm's ecosystem, specifically targeting developers involved in the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and metadata, ultimately aiming to inflate developer reputation scores. Its malicious behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on affected packages.
Vulnerability Detail
The vulnerability in regulatory_shark_z3n originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which can lead to the pollution of the npm registry. This behavior can compromise the security of applications that inadvertently depend on these malicious packages, potentially leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall regulatory_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 temporary workaround, consider using npm audit to identify and remove any dependencies that may have been affected by this malicious package. You can run the following command: npm audit fix.
Conclusion
The regulatory_shark_z3n package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for regulatory_shark_z3n →
FAQ
regulatory_shark_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the regulatory_shark_z3n package immediately and audit your project for any other affected dependencies.
Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
