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

layla-poke96 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158086: Malicious code in layla-poke96 (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 Penetration testing for web, API and mobile 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-poke96' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation and publication of derivative packages. The malicious nature of this package poses a significant risk to developers and users who may unknowingly incorporate it into their projects.

Vulnerability Detail

The vulnerability in 'layla-poke96' originates from its association with the tea.xyz token reward campaign. It contains scripts designed to automatically modify package.json files, removing private flags and changing version numbers. This allows the package to generate random names and continuously republish variants, polluting the npm registry. The ramifications include potential security risks for developers who may inadvertently use these malicious packages, leading to compromised applications and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall layla-poke96

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-poke96' and any other packages that may be part of the malicious campaign. Regularly audit your package dependencies using tools like npm audit to identify and remove any potentially harmful packages.

Conclusion

The 'layla-poke96' package poses a significant threat due to its malicious code designed to manipulate package management processes. It is crucial for developers to be vigilant and regularly audit their dependencies to maintain the integrity and security of their applications. Utilizing tools like Vulert can enhance your ability to monitor for vulnerabilities effectively.

See every vulnerability recorded for layla-poke96 →

Share this vulnerability

FAQ

'layla-poke96' is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The malicious code modifies package.json files, potentially leading to the inclusion of harmful packages and compromising the security of your application.

You should uninstall 'layla-poke96' immediately using the command 'npm uninstall layla-poke96' and audit your project for any other malicious packages.

Regularly audit your dependencies using tools like npm audit, and consider using Vulert to monitor your project for open-source vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by vulnerabilities without needing to install anything.

How To Fix

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

npm uninstall layla-poke96

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