Malicious Code Vulnerability in striking_mink_dumbs Package
Summary
MAL-2025-109193: Malicious code in striking_mink_dumbs (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 striking_mink_dumbs package is part of the npm ecosystem and has been identified as a component of a token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate the automatic generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the campaign. The malicious nature of this package poses significant risks to the integrity of the npm registry and the security of applications relying on it.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the striking_mink_dumbs package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby flooding the npm registry with potentially harmful variants. The ramifications include the pollution of the npm ecosystem, which can lead to security risks for developers and users who may inadvertently install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall striking_mink_dumbsIf 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 the striking_mink_dumbs package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include this package in its dependencies. You can also use tools like Vulert to monitor your project for vulnerabilities. For example, you can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The striking_mink_dumbs 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 from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for striking_mink_dumbs →
FAQ
The striking_mink_dumbs package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may contain malicious code that can harm your application or compromise user data.
If you have installed the striking_mink_dumbs package, you should uninstall it immediately using 'npm uninstall striking_mink_dumbs' and check your project for any other affected packages.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities without any signup at the Vulert playground.
To prevent future vulnerabilities, regularly update your dependencies, use tools like Vulert for monitoring, and review your package.json and package-lock.json files for any suspicious packages.
