Malicious Code Injection in typical_rook_0xrequest Package
Summary
MAL-2025-109902: Malicious code in typical_rook_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 typical_rook_0xrequest package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users and developers relying on this package.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the typical_rook_0xrequest package. This code modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and 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 typical_rook_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, consider removing the typical_rook_0xrequest package from your project until a secure version is released. You can do this by executing: npm uninstall typical_rook_0xrequest. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The typical_rook_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to take immediate action by updating or removing the package and monitoring their applications for vulnerabilities.
See every vulnerability recorded for typical_rook_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code can modify your package.json file, potentially exposing sensitive data and compromising your application's integrity.
You should uninstall the package immediately and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
