Malicious Code Injection in layla-poke70: A Threat to npm Packages

layla-poke70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

layla-poke70 is an npm package that is part of a broader ecosystem of packages often used in JavaScript development. It is typically utilized for various functionalities within applications. However, this package has been identified as part of a malicious campaign that aims to exploit npm's package management system by flooding it with derivative packages that can inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in layla-poke70 arises from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which can pollute the npm registry and potentially compromise the integrity of other packages. The malicious code is designed to automate the creation and publication of these packages, making it difficult for developers to track and manage their dependencies effectively.

How To Fix

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

npm uninstall layla-poke70

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 remove the layla-poke70 package from your project by executing the following command: npm uninstall layla-poke70. This will prevent any malicious code from executing within your application until a secure version is released.

Conclusion

The layla-poke70 package has been identified as containing malicious code that poses a significant risk to npm users. It is essential to take immediate action by updating or removing the package to safeguard your application from potential threats. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for layla-poke70 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application's dependencies.

You should update the package to a patched version if available or remove it from your project to mitigate the risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

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

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