Malicious Code Injection in layla-poke83: A Threat to npm Packages
Summary
MAL-2025-158072: Malicious code in layla-poke83 (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-poke83' is part of the npm ecosystem, which is widely used for JavaScript package management. It 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 designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'layla-poke83' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised package integrity, potential exposure of sensitive data, and a degraded developer reputation system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke83If 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 remove the 'layla-poke83' package from your project by executing 'npm uninstall layla-poke83'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'layla-poke83' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay informed about such vulnerabilities, regularly update their packages, and utilize tools like Vulert to monitor their applications for potential threats.
See every vulnerability recorded for layla-poke83 →
FAQ
The malicious code modifies package metadata to remove private flags and generates random package names, which can lead to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without needing to sign up.
Using compromised packages can lead to data exposure, security breaches, and a loss of trust in the software development process.
Regularly updating packages, using automated tools like Vulert for monitoring vulnerabilities, and adhering to best practices in package management can help prevent such issues.
If you have installed 'layla-poke83', you should uninstall it immediately and check for any updates or patches before reinstalling.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
