Malicious Code Injection in layla-poke62: A Threat to npm Users
Summary
MAL-2025-158049: Malicious code in layla-poke62 (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
layla-poke62 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify essential files and republish variants, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in layla-poke62 originates from its design to include autopublish scripts that manipulate the package.json file. This manipulation removes private flags and alters version numbers, allowing the package to generate random names and continuously republish itself. The ramifications of this vulnerability include the pollution of the npm registry with malicious packages, which can lead to security risks for developers who unknowingly integrate these packages into their projects. The technical aspects involve the use of scripts like auto.js and autopublish.js, which automate the malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke62If 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include layla-poke62 in its dependencies. Additionally, consider using Vulert to monitor your project 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-poke62 package poses a significant risk to npm users due to its malicious code injection capabilities. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert. By staying informed and proactive, developers can protect their applications from potential threats.
See every vulnerability recorded for layla-poke62 →
FAQ
layla-poke62 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall layla-poke62' and check for any dependencies that may rely on it.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
