Malicious Code Injection in layla-poke51: A Threat to npm Users
Summary
MAL-2025-158037: Malicious code in layla-poke51 (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-poke51 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in layla-poke51 originates 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 automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also leads to potential security risks for users who may unknowingly install these malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke51If 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-poke51 and any other packages that are part of the malicious campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before installation.
Conclusion
The layla-poke51 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. Users are advised to uninstall the package and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for layla-poke51 →
FAQ
layla-poke51 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic publication of derivative packages.
The vulnerability can lead to the installation of malicious packages that compromise the integrity of your project and potentially expose it to security risks.
You should immediately uninstall the package using npm uninstall layla-poke51 and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
