Malicious Code Injection in classic_octopus_0xrequest Package
Summary
MAL-2025-100576: Malicious code in classic_octopus_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 classic_octopus_0xrequest package is part of the npm ecosystem, primarily used for JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often include scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability in the classic_octopus_0xrequest package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of applications that depend on this package. The malicious payload can affect the security and reliability of software projects, making them susceptible to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall classic_octopus_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 remove the classic_octopus_0xrequest package from your project by executing the command: 'npm uninstall classic_octopus_0xrequest'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The classic_octopus_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and republishing behavior. It is essential for developers to take immediate action by updating or removing the package to protect their applications from potential exploitation.
See every vulnerability recorded for classic_octopus_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.
The vulnerability can lead to unauthorized modifications in your package.json file, affecting the integrity and security of your application.
You should immediately update or uninstall the classic_octopus_0xrequest package to mitigate the risk of exploitation.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
