Malicious Code Injection in cici-lengko4-pore: A Threat to npm Ecosystem

cici-lengko4-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97648: Malicious code in cici-lengko4-pore (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'cici-lengko4-pore' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish unauthorized derivatives, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in 'cici-lengko4-pore' originates from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks.

How To Fix

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

npm uninstall cici-lengko4-pore

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 'cici-lengko4-pore' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities. For example, you can check your application by using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The cici-lengko4-pore package poses a significant risk due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to remove this package from their projects and monitor for any potential vulnerabilities using tools like Vulert.

See every vulnerability recorded for cici-lengko4-pore →

Share this vulnerability

FAQ

cici-lengko4-pore is an npm package that is part of a malicious campaign designed to inflate developer reputation scores through the automatic publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further security risks.

You should uninstall the cici-lengko4-pore package immediately using 'npm uninstall cici-lengko4-pore' and monitor your project for any further vulnerabilities.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner.

Currently, there is no specific patch for the cici-lengko4-pore package. The best course of action is to uninstall the package and look for alternatives.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall cici-lengko4-pore

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