Malicious Code Injection in layla-poke31: A Threat to npm Ecosystem
Summary
MAL-2025-158015: Malicious code in layla-poke31 (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-poke31' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign targeting developers by flooding the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous variants of the original package, often with altered metadata.
Vulnerability Detail
The vulnerability in 'layla-poke31' originates from its association with the tea.xyz token reward campaign, which utilizes autopublish scripts to manipulate package metadata. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry, potentially affecting developers who rely on these packages for legitimate purposes. The ramifications include compromised package integrity, loss of trust in the npm ecosystem, and potential security risks for applications using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke31If 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 workaround, you can avoid using 'layla-poke31' and any other packages associated with the tea.xyz campaign. Instead, look for alternative packages that provide similar functionality without the associated risks. You can also use the following command to uninstall the package: npm uninstall layla-poke31.
Conclusion
The 'layla-poke31' package poses a significant 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 help maintain the security of your software.
See every vulnerability recorded for layla-poke31 →
FAQ
'layla-poke31' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall 'layla-poke31' immediately and monitor your application for any unusual behavior.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
