Malicious Code Injection in creative_shark_0xrequest Package
Summary
MAL-2025-101060: Malicious code in creative_shark_0xrequest (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 creative_shark_0xrequest package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign linked to the tea.xyz token reward initiative. This package is designed to automatically generate and publish derivative packages, which can lead to significant issues in the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the creative_shark_0xrequest package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores through the automatic publication of numerous derivative packages, leading to pollution of the npm registry and potential security risks for users of the package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall creative_shark_0xrequestIf 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 creative_shark_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The creative_shark_0xrequest package poses significant security risks due to its malicious code designed to manipulate npm registry entries. It is essential to uninstall this package and monitor for any updates or alternative solutions to safeguard your projects.
See every vulnerability recorded for creative_shark_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the automatic generation of malicious packages, polluting the npm registry and potentially compromising your project's security.
You should uninstall the package immediately using npm uninstall creative_shark_0xrequest and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
