Malicious Code Injection in layla-poke67: A Threat to npm Users
Summary
MAL-2025-158054: Malicious code in layla-poke67 (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-poke67' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that alters critical package metadata.
Vulnerability Detail
The vulnerability in 'layla-poke67' originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry. This can result in unauthorized access to sensitive data and compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall layla-poke67If 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-poke67' package from your project by executing the command: 'npm uninstall layla-poke67'. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The 'layla-poke67' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Users are advised to uninstall the package and monitor for updates. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for layla-poke67 →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring you stay informed about potential threats.
Regularly audit your dependencies, use trusted sources for packages, and keep your packages updated to minimize the risk of vulnerabilities.
