Malicious Code Injection in unable_penguin_requirement Package
Summary
MAL-2025-97087: Malicious code in unable_penguin_requirement (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 unable_penguin_requirement package is part of the npm ecosystem, commonly used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the unable_penguin_requirement package originates from its association with a malicious campaign that uses autopublish scripts to generate and publish derivative packages with randomized names. This manipulation includes altering the package.json file to remove private flags, changing version numbers, and continuously republishing variants to pollute the npm registry. The ramifications include potential exposure of sensitive data, compromised application integrity, and a polluted npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unable_penguin_requirementIf 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 unable_penguin_requirement package from your project by running: npm uninstall unable_penguin_requirement. Additionally, consider using npm audit to identify and address any other vulnerabilities in your dependencies.
Conclusion
The unable_penguin_requirement package poses a significant risk due to its malicious code injection vulnerability. It is crucial for developers to take immediate action by updating or removing the package to protect their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for unable_penguin_requirement →
FAQ
It is an npm package that has been linked to a malicious campaign aimed at manipulating package metadata for token rewards.
The vulnerability can lead to compromised application integrity, exposure of sensitive data, and pollution of the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If no patched version is available, it is advisable to remove the package from your project to mitigate risks.
Consider using Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json.
