Malicious Code Injection in obvious_mink_requirement Package
Summary
MAL-2025-95723: Malicious code in obvious_mink_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 'obvious_mink_requirement' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that modifies essential package files.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'obvious_mink_requirement' package. This payload alters the package.json file by removing private flags, changing version numbers, and generating random package names, primarily themed around Indonesian culture. The malicious code continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall obvious_mink_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 'obvious_mink_requirement' package from your project by executing the command: 'npm uninstall obvious_mink_requirement'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'obvious_mink_requirement' package contains a significant vulnerability due to malicious code that alters package files and republishing behavior. It is crucial to take immediate action by updating or uninstalling the package to safeguard your project from potential threats.
See every vulnerability recorded for obvious_mink_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time 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.
