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

layla-poke4 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158024: Malicious code in layla-poke4 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

layla-poke4 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm ecosystem, but it has been compromised to include malicious code. The vulnerability arises from the package's ability to modify its own metadata and publish variants, which can lead to significant issues in the npm registry.

Vulnerability Detail

The vulnerability in layla-poke4 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior is intended to inflate developer reputation scores for token rewards, ultimately polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers.

How To Fix

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

npm uninstall layla-poke4

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-poke4 package from your project by executing the command: 'npm uninstall layla-poke4'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The layla-poke4 package has been identified as containing malicious code that poses a significant risk to developers using npm. It is crucial to take immediate action by updating or uninstalling the package to safeguard your projects from potential exploitation.

See every vulnerability recorded for layla-poke4 →

Share this vulnerability

FAQ

layla-poke4 is an npm package that has been compromised to include malicious code aimed at manipulating the npm registry.

The malicious code can modify your package.json file, remove private flags, and publish unauthorized variants, which can lead to security vulnerabilities in your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If you cannot update the package, consider uninstalling it as a temporary measure to prevent potential exploitation.

Detailed information about this vulnerability can be found in the official npm advisory or through security monitoring tools like Vulert.

How To Fix

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

npm uninstall layla-poke4

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