Malicious Code Detected in 'ashamed-harlequin-pheasant' Package - npm Vulnerability
Summary
MAL-2025-93273: Malicious code in ashamed-harlequin-pheasant (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 'ashamed-harlequin-pheasant' package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
This vulnerability originates from a malicious payload embedded within the 'ashamed-harlequin-pheasant' package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, often themed around Indonesian culture. The continuous republishing of these variants can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ashamed-harlequin-pheasantIf 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 package by using the npm command: npm uninstall ashamed-harlequin-pheasant. Additionally, consider using npm audit to identify and address other vulnerabilities in your project.
Conclusion
The 'ashamed-harlequin-pheasant' package poses a significant risk due to its malicious code that modifies essential files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security.
See every vulnerability recorded for ashamed-harlequin-pheasant →
FAQ
It is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially compromising your project's integrity.
You should uninstall the package immediately and monitor your project for any other vulnerabilities using npm audit.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
