Malicious Code Injection in classic_firefly-toolteadev Package
Summary
MAL-2025-100574: Malicious code in classic_firefly-toolteadev (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 classic_firefly-toolteadev package is part of the npm ecosystem, primarily used for development tools in JavaScript applications. It is designed to facilitate various development tasks, but it has been compromised, making it susceptible to malicious activities that can affect developers and their projects.
Vulnerability Detail
This vulnerability originates from a malicious payload embedded in the classic_firefly-toolteadev package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the automatic publication of derivative packages. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, ultimately polluting the npm registry and potentially compromising other projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall classic_firefly-toolteadevIf 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 classic_firefly-toolteadev 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 classic_firefly-toolteadev package has been compromised with malicious code that can affect developers and their projects. It is crucial to uninstall this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help keep your application secure from such vulnerabilities.
See every vulnerability recorded for classic_firefly-toolteadev →
FAQ
It is a development tool package in the npm ecosystem, used for various JavaScript development tasks.
The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project and its dependencies.
You should uninstall the classic_firefly-toolteadev package immediately and check for any unauthorized changes in your project files.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
