Malicious Code Injection in tight_herring_0xrequest Package
Summary
MAL-2025-109697: Malicious code in tight_herring_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 tight_herring_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata.
Vulnerability Detail
The vulnerability originates from the presence of malicious code within the tight_herring_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses significant risks to developers relying on the integrity of npm packages, potentially leading to security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tight_herring_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 tight_herring_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to check for vulnerabilities in your project.
Conclusion
The tight_herring_0xrequest package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial to remove this package and monitor your project for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for tight_herring_0xrequest →
FAQ
It is an npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.
The malicious code modifies your package.json, removes private flags, and can lead to the pollution of the npm registry, affecting the integrity of your project.
You should uninstall the package immediately using 'npm uninstall tight_herring_0xrequest' and check for any alternative packages.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected, without requiring any signup.
