Malicious Code Injection in layla-poke86: A Threat to npm Ecosystem
Summary
MAL-2025-158075: Malicious code in layla-poke86 (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-poke86' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development of applications by allowing developers to share and reuse code. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in 'layla-poke86' stems from its association with a malicious campaign that generates and publishes numerous derivative packages with randomized names. This is achieved through scripts that modify the package.json file to remove private flags, alter version numbers, and continuously republish variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke86If 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 the 'layla-poke86' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package management practices to monitor and vet the packages you include in your projects.
Conclusion
The 'layla-poke86' package poses a significant threat to the npm ecosystem due to its malicious code that manipulates the registry. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor vulnerabilities in their projects.
See every vulnerability recorded for layla-poke86 →
FAQ
The vulnerability involves malicious code that modifies package.json to publish derivative packages, compromising the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in your software by analyzing package-lock.json. Visit Vulert Scanner to check for vulnerabilities without signup.
Using compromised packages can lead to security breaches, data leaks, and a loss of trust in the software supply chain.
Implementing strict package management practices, regularly updating dependencies, and using tools like Vulert can help prevent vulnerabilities.
Remove the package immediately and look for alternatives. Ensure to audit your project for any other potentially compromised packages.
