Malicious Code Vulnerability in distinct_penguin_0xrequest Package
Summary
MAL-2025-101645: Malicious code in distinct_penguin_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 distinct_penguin_0xrequest package is part of a larger ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications that depend on these packages.
Vulnerability Detail
The vulnerability in the distinct_penguin_0xrequest package arises from its malicious payload, which 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, polluting the npm registry and potentially compromising the security of applications that utilize these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood npm with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall distinct_penguin_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 distinct_penguin_0xrequest package and replace it with a similar, trusted package that provides the required functionality without the associated risks.
Conclusion
The distinct_penguin_0xrequest package poses a significant risk due to its malicious behavior, which can compromise the integrity of applications relying on it. It is crucial to remove this package and monitor for similar vulnerabilities using tools like Vulert to ensure the security of your software.
See every vulnerability recorded for distinct_penguin_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity and security of your application if it relies on affected packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can check for vulnerabilities without requiring installation.
You should uninstall the distinct_penguin_0xrequest package immediately and replace it with a trusted alternative.
Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and only install packages from trusted sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
