Malicious Code Injection in nuclear_porcupine_0xrequest Package
Summary
MAL-2025-106405: Malicious code in nuclear_porcupine_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
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 nuclear_porcupine_0xrequest package is part of the npm ecosystem, typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. This package contains scripts that automatically generate and publish derivative packages with randomized names, leading to potential misuse and pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious design of the nuclear_porcupine_0xrequest package, which includes scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to the proliferation of untrustworthy packages in the npm registry, compromising the integrity of the ecosystem and potentially exposing users to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nuclear_porcupine_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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. You can also use the following command to uninstall the package: npm uninstall nuclear_porcupine_0xrequest.
Conclusion
The nuclear_porcupine_0xrequest package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove this package from their projects to maintain the security of their applications.
See every vulnerability recorded for nuclear_porcupine_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 installation of untrustworthy packages, potentially compromising the security and integrity of your application.
You should uninstall the nuclear_porcupine_0xrequest package immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring 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.
