Malicious Code Injection in layla-poke35: A Threat to npm Packages
Summary
MAL-2025-158019: Malicious code in layla-poke35 (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-poke35' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality through third-party libraries. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in 'layla-poke35' stems 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. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke35If 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 'layla-poke35' and any other packages that may be part of the malicious campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'layla-poke35' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and regularly audit their dependencies to maintain the security and integrity of their applications.
See every vulnerability recorded for layla-poke35 →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Uninstall the package immediately using 'npm uninstall layla-poke35' and audit your project for any other potentially compromised packages.
While specific exploits have not been detailed, the manipulation of package metadata can lead to security breaches and reputation damage for developers.
Regularly audit your dependencies, use trusted sources for packages, and stay informed about known vulnerabilities in the npm ecosystem.
