Malicious Code Injection in interim_kingfisher-toolteadev Package
Summary
MAL-2025-104334: Malicious code in interim_kingfisher-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 interim_kingfisher-toolteadev package is part of the npm ecosystem, often utilized in JavaScript projects for various development tasks. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that republish variants with altered metadata.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the interim_kingfisher-toolteadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, thereby polluting the npm registry and potentially compromising the integrity of dependent projects. The source of this vulnerability is linked to a token reward campaign that exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall interim_kingfisher-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 prevent the package from being used in your project by removing it from your package.json file and ensuring that your application does not reference it in any scripts.
Conclusion
The interim_kingfisher-toolteadev package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised variants. It is essential to remove this package from your projects and monitor for similar vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for interim_kingfisher-toolteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code can compromise the integrity of your project by modifying package metadata and republishing variants, which may lead to dependency issues.
You should uninstall the package immediately using npm uninstall interim_kingfisher-toolteadev and check your project for any dependencies that may be affected.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review package sources before installation.
