Malicious Code Injection in grieving_mastodon_z3n Package
Summary
MAL-2025-94752: Malicious code in grieving_mastodon_z3n (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 grieving_mastodon_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign. The package's functionality is compromised due to its malicious intent.
Vulnerability Detail
The vulnerability originates from the package's 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 pollution of the npm registry. The malicious payload can significantly affect developers by inflating their reputation scores through deceptive practices, ultimately undermining the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall grieving_mastodon_z3nIf 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 manually remove the package from your project by running the command: npm uninstall grieving_mastodon_z3n. Additionally, consider using tools like Vulert to monitor your project for 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 grieving_mastodon_z3n package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be aware of such vulnerabilities and take immediate action to protect their projects. Regular monitoring and updates are essential to maintain the integrity of your software.
See every vulnerability recorded for grieving_mastodon_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and inflate developer reputation scores through deceptive practices.
You should uninstall the grieving_mastodon_z3n package immediately and check for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
