Malicious Code Injection in 'thirsty_shark_z3n' Package - npm Vulnerability
Summary
MAL-2025-109623: Malicious code in thirsty_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'thirsty_shark_z3n' package is part of the npm ecosystem, typically used for various JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanism. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'thirsty_shark_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall thirsty_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, you can avoid using the 'thirsty_shark_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The 'thirsty_shark_z3n' package poses a significant security risk due to its malicious code that alters package metadata and publishes compromised versions. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for thirsty_shark_z3n →
FAQ
The 'thirsty_shark_z3n' package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
Using the 'thirsty_shark_z3n' package can expose your application to security risks, including the potential for malicious code execution and dependency pollution.
You should remove the 'thirsty_shark_z3n' package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
