Malicious Code Injection in layla-poke61: A Threat to npm Ecosystem
Summary
MAL-2025-158048: Malicious code in layla-poke61 (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-poke61' 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 and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry, leading to significant security concerns for developers and users alike.
Vulnerability Detail
The vulnerability in 'layla-poke61' stems from its association with a malicious campaign that floods the npm registry with derivative packages. This package contains scripts designed to automatically modify its own package.json file, removing private flags, altering version numbers, and generating random package names. The result is a pollution of the npm registry, which can mislead developers and compromise the integrity of the software supply chain. The malicious code can lead to unauthorized access and manipulation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke61If 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 the 'layla-poke61' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your package dependencies for any signs of malicious activity.
Conclusion
The 'layla-poke61' package poses a significant security threat due to its malicious code designed to manipulate the npm registry. Developers are urged to remove this package from their projects and remain vigilant about the integrity of their dependencies. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for layla-poke61 →
FAQ
The malicious code can lead to unauthorized modifications in your project, potentially compromising your application's security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Currently, there is no patched version available for layla-poke61. It is recommended to uninstall the package and avoid using it.
The malicious code generates and publishes numerous derivative packages, polluting the npm registry and potentially misleading developers about the reliability of packages.
Immediately uninstall the package and review your project's dependencies for any other potentially malicious packages. Ensure to replace it with a trusted alternative.
