Malicious Code Injection in layla-poke16: A Threat to npm Users
Summary
MAL-2025-157998: Malicious code in layla-poke16 (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-poke16' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it 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 behavior not only compromises the integrity of the npm registry but also poses significant risks to developers who may unknowingly use these tainted packages.
Vulnerability Detail
The vulnerability in 'layla-poke16' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This can have serious ramifications, including the potential for developers to inadvertently install compromised packages, leading to 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-poke16If 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-poke16' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'layla-poke16' package presents a significant security risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for layla-poke16 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should remove the package from your project immediately and look for alternatives.
While the primary exploit involves the pollution of the npm registry, it can lead to further security issues if compromised packages are installed by developers.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
