Malicious Code Injection in layla-poke32: A Threat to npm Users
Summary
MAL-2025-158016: Malicious code in layla-poke32 (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
layla-poke32 is a package within the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that exploits npm's package management system. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant security risks for users.
Vulnerability Detail
The vulnerability in layla-poke32 stems from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to identify legitimate packages. This poses a risk of unintentional installation of compromised packages, leading to potential data breaches or system compromises.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke32If 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 layla-poke32 and any packages that may have been published as part of the same malicious campaign. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner without needing to sign up.
Conclusion
The layla-poke32 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive steps can help safeguard your projects from potential threats.
See every vulnerability recorded for layla-poke32 →
FAQ
layla-poke32 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the installation of compromised packages, which may result in data breaches or system compromises.
You should uninstall the package immediately using 'npm uninstall layla-poke32' and check your project for any other affected packages.
Regularly update your dependencies, monitor your package-lock.json file for vulnerabilities, and use tools like Vulert for real-time alerts.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
