Malicious Code Injection in layla-poke65: A Threat to npm Ecosystem
Summary
MAL-2025-158052: Malicious code in layla-poke65 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package layla-poke65 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in layla-poke65 stems from its association with the tea.xyz token reward campaign, which has been known to deploy malicious scripts. These scripts, such as auto.js and autopublish.js, are designed to automatically generate and publish numerous derivative packages with randomized names. This not only inflates developer reputation scores but also modifies the package.json file to remove private flags and alters version numbers. The continuous republishing of these variants leads to pollution of the npm registry, posing significant risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke65If 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-poke65 package until a secure version is released. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The layla-poke65 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to stay vigilant, update their packages, and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for layla-poke65 →
FAQ
layla-poke65 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should immediately update the package to a patched version if available or remove it from your project to mitigate risks.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
