Malicious Code Injection in technical-alonbio-toli: A Threat to npm Packages
Summary
MAL-2025-168908: Malicious code in technical-alonbio-toli (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 'technical-alonbio-toli' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to inflate developer reputation scores through the automated generation and publication of derivative packages. The malicious behavior includes modifying package metadata and republishing variants, which can lead to pollution of the npm registry and potential security risks for users.
Vulnerability Detail
The vulnerability in 'technical-alonbio-toli' originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically alter the package.json file, removing private flags and changing version numbers. This allows the package to continuously republish itself under random names, which can mislead developers and users, ultimately compromising the integrity of the npm registry. The ramifications include the potential for malicious code to be inadvertently used in projects, leading to security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall technical-alonbio-toliIf 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 remove the 'technical-alonbio-toli' package from your project by executing the command: 'npm uninstall technical-alonbio-toli'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'technical-alonbio-toli' package poses a significant security risk due to its malicious behavior of modifying and republishing itself. It is crucial for developers to take immediate action by uninstalling the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of open-source projects.
See every vulnerability recorded for technical-alonbio-toli →
FAQ
The vulnerability involves malicious scripts that modify package metadata and republish the package under random names, potentially leading to security risks.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
It is advisable to uninstall the package immediately and check for updates or alternatives that do not pose security risks.
Yes, the impacts include potential exposure to malicious code and the pollution of the npm registry, which can affect other developers and projects.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
