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

lala-poke33 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157957: Malicious code in lala-poke33 (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 'lala-poke33' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been known to flood the npm registry with malicious packages. The primary function of such packages is to inflate developer reputation scores through the automatic generation and publishing of derivative packages. However, this functionality has been compromised, leading to significant security risks.

Vulnerability Detail

The vulnerability in 'lala-poke33' stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall lala-poke33

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, you can avoid using 'lala-poke33' and any other packages that are part of the token reward campaign. You can also use the following command to uninstall the package: npm uninstall lala-poke33.

Conclusion

The 'lala-poke33' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for lala-poke33 →

Share this vulnerability

FAQ

'lala-poke33' is an npm package that has been identified as malicious, designed to inflate developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, potentially leading to unauthorized access and data breaches, as well as polluting the npm registry.

You should uninstall 'lala-poke33' immediately and check for any other potentially compromised packages in your project.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall lala-poke33

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