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

lala-poke40 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157965: Malicious code in lala-poke40 (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-poke40' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality through third-party libraries. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing numerous derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability in 'lala-poke40' stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The malicious payload can potentially compromise the integrity of applications relying on this package, allowing for unauthorized access or manipulation of data.

How To Fix

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

npm uninstall lala-poke40

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-poke40' and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The 'lala-poke40' package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for lala-poke40 →

Share this vulnerability

FAQ

'lala-poke40' is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to unauthorized modifications in your application, potentially compromising data integrity and security.

You should uninstall 'lala-poke40' immediately using 'npm uninstall lala-poke40' and consider using alternative packages.

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

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

How To Fix

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

npm uninstall lala-poke40

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