Malicious Code Injection in layla-poke33: A Threat to npm Ecosystem
Summary
MAL-2025-158017: Malicious code in layla-poke33 (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 layla-poke33 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 various malicious activities. The primary function of such packages is to facilitate the distribution of JavaScript code, but in this case, it has been compromised to serve malicious purposes.
Vulnerability Detail
The vulnerability in layla-poke33 stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke33If 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 avoid using layla-poke33 and any other packages associated with the tea.xyz token reward campaign. Instead, look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The layla-poke33 package poses a significant threat to the npm ecosystem due to its malicious code that modifies project configurations and repopulates the npm registry with compromised packages. It is essential for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for layla-poke33 →
FAQ
layla-poke33 is an npm package that has been identified as malicious due to its involvement in a token reward campaign that floods the npm registry with compromised packages.
Using layla-poke33 can lead to security breaches, as the malicious code can modify your project's configuration and introduce vulnerabilities.
You should immediately uninstall layla-poke33 and review your project for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
