Malicious Code Injection in Respective_Shark_Z3N Package - npm Vulnerability
Summary
MAL-2025-96330: Malicious code in respective_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 respective_shark_z3n package is part of the npm ecosystem, primarily utilized for various JavaScript applications. It has been identified as part of a broader malicious campaign that aims to exploit npm's package management system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with random names.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the respective_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 malicious payload is part of a larger scheme associated with the tea.xyz token reward campaign, which aims to manipulate npm's reputation system by flooding it with numerous derivative packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respective_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check for vulnerabilities in your application without any installation. Use the following command to remove the package: npm uninstall respective_shark_z3n.
Conclusion
The respective_shark_z3n package poses a significant risk due to its malicious code designed to manipulate npm's package management system. It is crucial to uninstall this package and monitor your application for vulnerabilities using tools like Vulert.
See every vulnerability recorded for respective_shark_z3n →
FAQ
The respective_shark_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating npm's package management system.
The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and pollution of the npm registry.
You should uninstall the respective_shark_z3n package immediately and check for any updates or patches that may address this vulnerability.
You can use Vulert to monitor your application for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
