Malicious Code Injection in layla-poke53: A Threat to npm Users

layla-poke53 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158039: Malicious code in layla-poke53 (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-poke53 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, making it a vector for malicious activities. The vulnerability stems from its association with a series of autopublish scripts that generate and publish derivative packages, which can lead to reputation inflation and registry pollution.

Vulnerability Detail

The vulnerability in layla-poke53 originates from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, which can clutter the npm registry and potentially lead to security risks for developers who may unknowingly use these compromised packages. The source of this vulnerability has been identified by Amazon Inspector, highlighting the need for vigilance in package management.

How To Fix

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

npm uninstall layla-poke53

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, consider removing the layla-poke53 package from your project until a secure version is released. You can do this by executing: npm uninstall layla-poke53. Additionally, you can monitor your dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time without requiring code access or installation.

Conclusion

The layla-poke53 package has been compromised with malicious code that poses a significant risk to developers using npm. It is crucial to update or remove the package to mitigate potential threats. Utilizing tools like Vulert can help monitor your dependencies for vulnerabilities in real-time.

See every vulnerability recorded for layla-poke53 →

Share this vulnerability

FAQ

layla-poke53 is an npm package associated with the tea.xyz token reward campaign, designed to facilitate certain functionalities within the npm ecosystem.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to security risks and clutter in the npm registry.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If an immediate update is not possible, consider uninstalling the package as a temporary measure and monitor your dependencies for any updates.

The vulnerability was identified by Amazon Inspector, which specializes in detecting malicious packages in the npm ecosystem.

How To Fix

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

npm uninstall layla-poke53

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