Malicious Code Injection in layla-poke12: A Threat to npm Packages
Summary
MAL-2025-157994: Malicious code in layla-poke12 (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 layla-poke12 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish derivatives to inflate developer reputation scores, posing a significant risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in layla-poke12 stems from its inclusion in a campaign that deploys malicious scripts designed to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks, as these malicious packages can execute harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke12
If 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 measure, you can avoid using the layla-poke12 package and replace it with a known safe alternative. Always verify the integrity of packages before installation.
Conclusion
The layla-poke12 package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your applications from potential security risks.
See every vulnerability recorded for layla-poke12 →
FAQ
layla-poke12 is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The vulnerability can lead to the installation of malicious code that may compromise your application's security and integrity, potentially leading to data breaches or other security incidents.
If you have installed layla-poke12, you should uninstall it immediately using 'npm uninstall layla-poke12' and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground at Vulert Scanner.
Yes, consider using well-established and trusted packages that serve similar functionalities. Always review package documentation and community feedback before installation.