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

layla-poke73 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158061: Malicious code in layla-poke73 (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-poke73' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like others in this campaign, is designed to manipulate npm's package registry by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this comes at the cost of security and integrity within the npm registry.

Vulnerability Detail

The vulnerability in 'layla-poke73' originates from its malicious design, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to a pollution of the npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, which can lead to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall layla-poke73

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 workaround, avoid using the 'layla-poke73' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which allows you to check your package-lock.json for open-source vulnerabilities in real-time.

Conclusion

The 'layla-poke73' package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities. By staying vigilant and informed, developers can protect their applications from potential security breaches.

See every vulnerability recorded for layla-poke73 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

You should uninstall the package immediately using 'npm uninstall layla-poke73' and look for alternative packages.

Yes, consider using other npm packages that provide similar functionality but are known to be secure and trustworthy.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall layla-poke73

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