Malicious Code Injection in layla-poke42: A Threat to npm Ecosystem

layla-poke42 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158027: Malicious code in layla-poke42 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

layla-poke42 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities. This package is designed to facilitate token rewards but has been compromised to include harmful scripts that manipulate package metadata and publish unauthorized variants. The vulnerability stems from the package's design, which allows for automatic publishing and modification of its contents, making it susceptible to exploitation.

Vulnerability Detail

The vulnerability in layla-poke42 originates from its association with the tea.xyz token reward campaign, which has led to the inclusion of malicious scripts. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This not only inflates developer reputation scores but also pollutes the npm registry with unauthorized packages. The ramifications include potential security risks for users who unknowingly install these compromised packages, leading to further exploitation and abuse within the npm ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall layla-poke42

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 workaround, you can remove the layla-poke42 package from your project by executing the following command: npm uninstall layla-poke42. This will prevent any malicious code from executing while you assess the situation and look for a secure alternative package.

Conclusion

The layla-poke42 package has been identified as containing malicious code that poses a significant threat to users and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to mitigate potential risks. Regular monitoring of your dependencies using tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for layla-poke42 →

Share this vulnerability

FAQ

layla-poke42 is an npm package that was part of a token reward campaign but has been compromised to include malicious code.

The malicious code can modify your package.json, remove private flags, and publish unauthorized package variants, posing security risks.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall layla-poke42

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback