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

lala-poke9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

lala-poke9 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with altered metadata. Its primary function is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol, making it a significant concern for developers relying on npm packages.

Vulnerability Detail

The vulnerability in lala-poke9 stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. This code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. The ramifications include pollution of the npm registry, potential security risks for applications using these packages, and the undermining of developer trust in the ecosystem.

How To Fix

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

npm uninstall lala-poke9

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 the lala-poke9 package and replace it with a trusted alternative. If you have already installed it, ensure to audit your npm packages using 'npm audit' to identify any other vulnerabilities.

Conclusion

The discovery of malicious code in the lala-poke9 package highlights the ongoing risks within the npm ecosystem. Developers must remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, the integrity of applications can be maintained.

See every vulnerability recorded for lala-poke9 →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately and audit your project for any other vulnerabilities using 'npm audit'.

Yes, consider using well-established and trusted npm packages that serve similar functionalities without the associated risks.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from reputable sources.

How To Fix

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

npm uninstall lala-poke9

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