Malicious Code Injection in layla-poke100: A Threat to npm Users

layla-poke100 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157992: Malicious code in layla-poke100 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'layla-poke100' 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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality has been compromised, making it a vector for malicious code that can affect users and developers alike.

Vulnerability Detail

The vulnerability in 'layla-poke100' stems from its involvement in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry. The ramifications include potential security risks for users who unknowingly install these compromised packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall layla-poke100

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 avoid using 'layla-poke100' and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using npm audit to check for vulnerabilities in your project and remove any affected packages.

Conclusion

The 'layla-poke100' package has been identified as a vector for malicious code, posing significant risks to users and the npm ecosystem. It is crucial to update or remove this package and utilize monitoring tools like Vulert to safeguard your projects against similar vulnerabilities.

See every vulnerability recorded for layla-poke100 →

Share this vulnerability

FAQ

layla-poke100 is an npm package that has been compromised and is associated with a malicious campaign aimed at inflating developer reputation scores.

The malicious code modifies your package.json file and can lead to the installation of additional compromised packages, posing security risks to your project.

If you have installed layla-poke100, you should remove it from your project and update your dependencies to ensure you are not using any compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

To prevent future vulnerabilities, regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for any potential threats.

How To Fix

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

npm uninstall layla-poke100

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