Malicious Code Injection in laila-getuk9-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74050: Malicious code in laila-getuk9-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'laila-getuk9-breki' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who might unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the 'laila-getuk9-breki' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random Indonesian-themed package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to security risks for developers who rely on these packages. The presence of autopublish scripts (auto.js, autopublish.js, etc.) further automates this malicious behavior, making it difficult to track and mitigate.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall laila-getuk9-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, avoid using the 'laila-getuk9-breki' package and consider alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package-lock.json file for any malicious dependencies.
Conclusion
The 'laila-getuk9-breki' package poses a significant threat due to its malicious code that alters project configurations and repopulates the npm registry with compromised packages. It is essential to remove this package and monitor your dependencies to maintain a secure development environment.
See every vulnerability recorded for laila-getuk9-breki →
FAQ
Using this package can lead to security vulnerabilities, as it modifies your project's package.json and introduces potentially harmful code.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the package using 'npm uninstall laila-getuk9-breki' and check for any other compromised packages in your project.
Yes, consider using reputable packages that offer similar functionality but do not have a history of malicious behavior.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
