Malicious Code Injection in layla-poke8 Package - npm Vulnerability

layla-poke8 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158068: Malicious code in layla-poke8 (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 layla-poke8 package is part of a broader ecosystem within npm, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm registry. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the layla-poke8 package stems from its association with a malicious campaign that floods the npm registry with derivative packages. This campaign modifies the package.json file to remove private flags, alters version numbers, and generates random package names, ultimately leading to the pollution of the npm registry. The malicious payload can inflate developer reputation scores fraudulently, posing risks to developers and users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall layla-poke8

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-poke8 package until a secure version is released. Additionally, you may want to implement stricter package validation processes in your development environment to prevent the installation of potentially malicious packages.

Conclusion

The layla-poke8 package has been identified as a vector for malicious code injection, posing significant risks to developers and users. It is essential to take immediate action by updating or removing the package and implementing monitoring tools like Vulert to safeguard against future vulnerabilities.

See every vulnerability recorded for layla-poke8 →

Share this vulnerability

FAQ

The layla-poke8 package is a JavaScript package available on npm, used for various functionalities in applications. However, it has been identified as part of a malicious campaign.

This vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security, potentially leading to data breaches or unauthorized access.

If you have installed the layla-poke8 package, it is recommended to update it to a patched version or remove it entirely from your project to mitigate risks.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground at Vulert Scanner.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools for vulnerability scanning, and maintain an updated list of packages to ensure you are using secure versions.

How To Fix

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

npm uninstall layla-poke8

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