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

layla-poke98 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The package 'layla-poke98' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the sharing and reuse of code among developers. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with harmful scripts. This vulnerability poses a significant risk to developers who may unknowingly integrate compromised packages into their applications.

Vulnerability Detail

The vulnerability in 'layla-poke98' originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload can lead to unauthorized access, data breaches, and the potential for further exploitation of affected systems.

How To Fix

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

npm uninstall layla-poke98

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 the 'layla-poke98' package and replace it with an alternative package that provides similar functionality without the associated risks. Always verify the integrity and source of packages before integrating them into your project.

Conclusion

The 'layla-poke98' package poses a significant risk due to its malicious code designed to exploit the npm ecosystem. Developers are urged to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for layla-poke98 →

Share this vulnerability

FAQ

The layla-poke98 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.

You should uninstall the package immediately using 'npm uninstall layla-poke98' and review your project's dependencies for any other potentially malicious packages.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Yes, you should look for alternative packages that provide similar functionality but have a verified and trusted reputation within the npm community.

How To Fix

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

npm uninstall layla-poke98

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