Malicious Code Injection in ida-klanting25-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73435: Malicious code in ida-klanting25-breki (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 package 'ida-klanting25-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores through automated publishing of derivative packages. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure and reliable software.
Vulnerability Detail
The vulnerability in 'ida-klanting25-breki' originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This malicious behavior can compromise the integrity of the npm ecosystem, allowing attackers to manipulate package dependencies and potentially introduce harmful code into applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ida-klanting25-brekiIf 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, consider removing the 'ida-klanting25-breki' package from your project if it is not essential. You can do this by executing the command: 'npm uninstall ida-klanting25-breki'. Additionally, monitor your package-lock.json file for any unexpected changes that may indicate the presence of malicious packages.
Conclusion
The 'ida-klanting25-breki' package poses a significant security risk due to its malicious code that alters package metadata and repackages it. Developers should take immediate action to remove or update this package to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for ida-klanting25-breki →
FAQ
The vulnerability involves malicious code that modifies package.json and repackages it with random names, leading to potential security risks.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Remove the package using 'npm uninstall ida-klanting25-breki' and update your dependencies to ensure security.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json.
As a workaround, consider removing the package and monitoring your project for any unusual behavior until you can implement a secure version.
