Malicious Code Injection in layla-poke3 Package - npm Vulnerability
Summary
MAL-2025-158013: Malicious code in layla-poke3 (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 layla-poke3 package is part of the npm ecosystem, often utilized for various JavaScript applications. This package has been identified as part of a broader malicious campaign that aims to exploit npm's package management system. The vulnerability stems from the package's involvement in generating and publishing derivative packages with altered metadata, which can lead to reputation inflation and potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in layla-poke3 originates from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names for derivative packages, which are then republished to the npm registry, polluting it with potentially harmful packages. The ramifications include compromised developer reputations, increased risk of dependency confusion, and exposure to malicious code for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke3If 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-poke3 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes using tools like Vulert.
Conclusion
The layla-poke3 package poses a significant security risk due to its involvement in a malicious npm campaign. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for layla-poke3 →
FAQ
layla-poke3 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.
You should remove the layla-poke3 package from your project immediately and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
