Malicious Code Injection in concerned_mastodon_dumbs Package
Summary
MAL-2025-100810: Malicious code in concerned_mastodon_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 concerned_mastodon_dumbs package is part of the npm ecosystem, primarily used for various functionalities within JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing of derivative packages, making it a significant security risk.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes malicious scripts to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting developers and their projects by compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall concerned_mastodon_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 measure, you can avoid using the concerned_mastodon_dumbs package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package-lock.json file to identify any potentially vulnerable packages.
Conclusion
The concerned_mastodon_dumbs package poses a significant security risk due to its malicious nature. It is crucial for developers to be aware of such vulnerabilities and take immediate action to protect their applications. Regular monitoring and auditing of dependencies can help mitigate these risks.
See every vulnerability recorded for concerned_mastodon_dumbs →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application by introducing malicious code.
You should uninstall the package immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
