Malicious Code Injection in lala-poke51: A Threat to npm Ecosystem

lala-poke51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157976: Malicious code in lala-poke51 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'lala-poke51' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with random names. The primary functionality of these packages is to inflate developer reputation scores for rewards associated with the tea protocol, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'lala-poke51' stems from its malicious code 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 variants, which pollutes the npm registry and can potentially compromise other packages and applications relying on npm. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the malicious activities.

How To Fix

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

npm uninstall lala-poke51

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 'lala-poke51' and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.

Conclusion

The 'lala-poke51' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for lala-poke51 →

Share this vulnerability

FAQ

'lala-poke51' is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to unauthorized changes in your package.json, potentially compromising your application and polluting the npm registry.

You should uninstall 'lala-poke51' immediately using 'npm uninstall lala-poke51' and review your other dependencies for security.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lala-poke51

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