Malicious Code Injection in lala-poke19: A Threat to npm Packages

lala-poke19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157941: Malicious code in lala-poke19 (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

The package 'lala-poke19' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the sharing and reuse of code among developers. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in 'lala-poke19' stems from its involvement in a malicious campaign associated with the tea.xyz token reward initiative. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and create random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can mislead developers and inflate reputation scores fraudulently.

How To Fix

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

npm uninstall lala-poke19

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 measure, avoid using 'lala-poke19' and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The 'lala-poke19' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant about the packages they use and to take immediate action if they are affected. Utilizing tools like Vulert can help maintain the integrity of your software projects.

See every vulnerability recorded for lala-poke19 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.

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 lala-poke19' and replace it with a trusted alternative.

This vulnerability can lead to the pollution of your project's dependencies, potentially causing conflicts and security risks.

Yes, regularly audit your dependencies, use trusted sources, and consider using tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall lala-poke19

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