Malicious Code Injection in layla-poke68: A Threat to npm Ecosystem
Summary
MAL-2025-158055: Malicious code in layla-poke68 (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-poke68' 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 exploit the npm registry by flooding it with derivative packages that have randomized names. This not only affects the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in 'layla-poke68' originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the automatic publication of numerous derivative packages, which can pollute the npm registry and inflate developer reputation scores fraudulently. The ramifications include potential security risks for developers who may inadvertently install these malicious packages, leading to compromised applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke68If 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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. Developers should avoid using any packages that are part of the tea.xyz token reward campaign.
Conclusion
The discovery of malicious code within the layla-poke68 package highlights the ongoing risks associated with open-source software. Developers must remain vigilant and proactive in managing their dependencies to safeguard their applications. Utilizing tools like Vulert can assist in monitoring for vulnerabilities and maintaining the integrity of the software supply chain.
See every vulnerability recorded for layla-poke68 →
FAQ
layla-poke68 is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
If your application uses the layla-poke68 package, it may be exposed to security risks due to the malicious scripts that modify package configurations and publish unauthorized packages.
You should uninstall the layla-poke68 package immediately using the command 'npm uninstall layla-poke68' and review your dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.
As of now, there are no patches for the layla-poke68 package. The best course of action is to remove the package and avoid using any related malicious packages.
