Malicious Code Injection in layla-poke41: A Threat to npm Ecosystem
Summary
MAL-2025-158026: Malicious code in layla-poke41 (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-poke41' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing derivative packages with harmful scripts. The vulnerability stems from its association with the tea.xyz token reward campaign, which has led to the proliferation of malicious packages designed to manipulate developer reputation scores.
Vulnerability Detail
The vulnerability in 'layla-poke41' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these malicious packages in their projects, potentially leading to security breaches and loss of data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke41If 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 'layla-poke41' and any other packages associated with the tea.xyz token reward campaign. Regularly check your package-lock.json file for any unauthorized changes and consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The 'layla-poke41' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for layla-poke41 →
FAQ
'layla-poke41' is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
Using 'layla-poke41' can lead to security risks, including unauthorized access to your code and potential data breaches.
You should remove 'layla-poke41' from your project and audit your dependencies for any other malicious packages.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
