Malicious Code Injection in wrong_stork_dumbs Package: A Threat to npm Users
Summary
MAL-2025-111043: Malicious code in wrong_stork_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 wrong_stork_dumbs package is part of a series of npm packages that have been identified as malicious. These packages are often associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. The functionality of these packages includes the automatic generation and publication of new packages with randomized names, which can lead to significant pollution of the npm registry and potential security risks for users.
Vulnerability Detail
The vulnerability in the wrong_stork_dumbs package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, which can lead to the continuous republishing of variants. The ramifications of this vulnerability include the potential for malicious code to be executed in user environments, the compromise of package integrity, and the pollution of the npm registry with unwanted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wrong_stork_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 workaround, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without requiring any signup.
Conclusion
The wrong_stork_dumbs package poses a significant threat to npm users due to its malicious code and the potential for widespread impact on the npm registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for wrong_stork_dumbs →
FAQ
The wrong_stork_dumbs package is an npm package identified as malicious, designed to inflate developer reputation scores through the automatic generation of derivative packages.
This vulnerability can lead to the execution of malicious code, compromise the integrity of your project, and pollute the npm registry with unwanted packages.
You should remove the wrong_stork_dumbs package from your project immediately and check for any updates or patches that may be available.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
