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

layla-poke74 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158062: Malicious code in layla-poke74 (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 package 'layla-poke74' is part of the npm ecosystem, which is a popular platform for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative packages, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'layla-poke74' originates from its association with malicious scripts designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. These scripts modify the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to pollution of the npm registry and potential exploitation by malicious actors.

How To Fix

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

npm uninstall layla-poke74

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 'layla-poke74' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages to identify and remove any suspicious or untrusted packages.

Conclusion

The 'layla-poke74' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and publish harmful derivatives. It is crucial to remove this package and regularly audit your dependencies to maintain the security of your applications.

See every vulnerability recorded for layla-poke74 →

Share this vulnerability

FAQ

'layla-poke74' is an npm package that has been identified as malicious due to its involvement in a token reward campaign that floods the npm registry with harmful packages.

The vulnerability can lead to the pollution of the npm registry, potentially allowing malicious actors to exploit your application through compromised packages.

You should immediately uninstall 'layla-poke74' using the command 'npm uninstall layla-poke74' and audit your project for any other suspicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. It requires only the package-lock.json file for real-time alerts.

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

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