Malicious Code Vulnerability in layla-poke19: A Threat to npm Users

layla-poke19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158001: Malicious code in layla-poke19 (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

layla-poke19 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to manipulate developer reputation scores by flooding the npm registry with derivative packages. The malicious nature of this package compromises its integrity and poses a significant risk to users who may unknowingly install it.

Vulnerability Detail

The vulnerability in layla-poke19 originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can result in developers inadvertently installing compromised packages, which may lead to security breaches or data loss.

How To Fix

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

npm uninstall layla-poke19

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, avoid using layla-poke19 and any packages that may have been derived from it. Regularly audit your project's dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The layla-poke19 package poses a significant threat due to its malicious code designed to manipulate npm's registry. Users are advised to uninstall the package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for layla-poke19 →

Share this vulnerability

FAQ

layla-poke19 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may result in security breaches or data loss.

You should uninstall the package immediately using 'npm uninstall layla-poke19' and audit your dependencies for any other vulnerabilities.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

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-poke19

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