Malicious Code Injection in layla-poke11: A Threat to npm Users
Summary
MAL-2025-157993: Malicious code in layla-poke11 (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-poke11' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages, potentially compromising the integrity of the npm registry and affecting developers' reputations.
Vulnerability Detail
The vulnerability in 'layla-poke11' originates from its association with the tea.xyz token reward campaign, which floods npm 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. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially leading to security risks for users who unknowingly install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke11If 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 measure, avoid using the 'layla-poke11' package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before installation.
Conclusion
The 'layla-poke11' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor their projects for vulnerabilities. By taking proactive measures, developers can safeguard their applications and maintain the integrity of their software.
See every vulnerability recorded for layla-poke11 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall layla-poke11' and review your project's dependencies for any other potentially malicious packages.
Yes, you should look for alternative packages that provide similar functionality but are verified and trusted within the community.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from reputable sources.
