Malicious Code Injection in udin-soto41-breki: A Threat to npm Packages
Summary
MAL-2025-75842: Malicious code in udin-soto41-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 'udin-soto41-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.
Vulnerability Detail
The vulnerability in 'udin-soto41-breki' originates from its association with a malicious campaign that utilizes autopublish scripts to alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects with malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall udin-soto41-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, you can remove the 'udin-soto41-breki' package from your project by executing: 'npm uninstall udin-soto41-breki'. This will prevent any malicious code from executing while you seek a secure alternative or wait for a patched version.
Conclusion
The 'udin-soto41-breki' package poses a significant risk due to its malicious code that alters package files and repopulates the npm registry with harmful variants. It is crucial for developers to monitor their dependencies, update to secure versions, and utilize tools like Vulert to ensure their projects remain safe from such vulnerabilities.
See every vulnerability recorded for udin-soto41-breki →
FAQ
The primary risk is the injection of malicious code that modifies package files and republish variants, leading to potential security breaches.
You can check your package.json or package-lock.json files for any references to 'udin-soto41-breki'.
You should uninstall the package immediately and look for a secure alternative or update to a patched version if available.
Yes, Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
