Malicious Code Injection in terrible_mink_0xrequest Package
Summary
MAL-2025-109558: Malicious code in terrible_mink_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 terrible_mink_0xrequest package is part of a series of npm packages that have been identified as malicious. These packages are associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The functionality of these packages is compromised, as they are designed to manipulate the npm registry rather than serve legitimate purposes.
Vulnerability Detail
The vulnerability in the terrible_mink_0xrequest package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the package management system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall terrible_mink_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 workaround, avoid using the terrible_mink_0xrequest package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like Vulert, which can monitor and alert you in real-time for open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The terrible_mink_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for terrible_mink_0xrequest →
FAQ
It is an npm package identified as malicious, part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the terrible_mink_0xrequest package immediately and check your project for any other affected packages.
Currently, there is no patched version available for the terrible_mink_0xrequest package.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.
