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

lala-poke60 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157986: Malicious code in lala-poke60 (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 'lala-poke60' is part of the npm ecosystem, which is widely used 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. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts. The presence of malicious code in 'lala-poke60' poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'lala-poke60' originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks, as these malicious packages can be used to execute harmful code or steal sensitive information.

How To Fix

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

npm uninstall lala-poke60

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 prevent the installation of 'lala-poke60' by using the following command: 'npm uninstall lala-poke60'. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you in real-time about open-source vulnerabilities.

Conclusion

The 'lala-poke60' package has been identified as containing malicious code that poses a significant threat to the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can further enhance security by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for lala-poke60 →

Share this vulnerability

FAQ

The vulnerability can lead to the modification of your package.json file, potentially allowing malicious code execution and compromising your project's security.

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

If you cannot update 'lala-poke60', it is advisable to remove it from your project to avoid potential security risks.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.

Regularly updating your dependencies, using trusted sources, and employing vulnerability monitoring tools like Vulert can help prevent similar issues.

How To Fix

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

npm uninstall lala-poke60

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