Malicious Code Exploit in panicky_mastodon_z3n Package
Summary
MAL-2025-89352: Malicious code in panicky_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 panicky_mastodon_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package is suspected to be involved in a token reward campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package poses significant risks to developers and users alike, as it can lead to the proliferation of harmful code within the npm registry.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for malicious code execution and the compromise of developer environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall panicky_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 temporary workaround, you can avoid using the panicky_mastodon_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The panicky_mastodon_z3n package presents a significant security risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.
See every vulnerability recorded for panicky_mastodon_z3n →
FAQ
It is an npm package suspected to be part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising your application's security and integrity.
You should remove the panicky_mastodon_z3n package from your project immediately and monitor your dependencies for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools that monitor for vulnerabilities, and stay informed about security advisories related to the packages you use.
