Malicious Code Injection in layla-poke27: A Threat to npm Ecosystem
Summary
MAL-2025-158010: Malicious code in layla-poke27 (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-poke27' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious software.
Vulnerability Detail
The vulnerability in 'layla-poke27' 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, polluting the npm registry. This can lead to unintentional installations of malicious packages by developers, compromising their applications and potentially leading to data breaches or other security incidents.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke27If 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-poke27' package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'layla-poke27' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is crucial for developers to remove this package and regularly audit their dependencies to maintain application security.
See every vulnerability recorded for layla-poke27 →
FAQ
The impact includes potential exposure to malicious code, which can compromise application security and integrity.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
If you have installed layla-poke27, you should uninstall it immediately and review your project for any unauthorized changes.
There are no patches available for layla-poke27 as it is recommended to remove the package entirely.
Regularly audit your dependencies, use trusted sources for packages, and monitor for vulnerabilities using tools like Vulert.
