Malicious Code Injection in bayu-lengko75-pore Package

bayu-lengko75-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97611: Malicious code in bayu-lengko75-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The bayu-lengko75-pore package is part of the npm ecosystem, primarily used for JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the bayu-lengko75-pore package, which contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these packages. The ramifications include compromised package integrity and potential security risks for applications relying on this package.

How To Fix

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

npm uninstall bayu-lengko75-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, avoid using the bayu-lengko75-pore package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your dependencies for any malicious packages.

Conclusion

The bayu-lengko75-pore package poses a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is crucial to remove this package from your projects and monitor your dependencies for similar threats.

See every vulnerability recorded for bayu-lengko75-pore →

Share this vulnerability

FAQ

The bayu-lengko75-pore package is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to compromised package integrity, allowing malicious code to be executed within your application, potentially exposing it to security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Immediately uninstall the bayu-lengko75-pore package and review your package-lock.json file for any references to it. Replace it with a safer alternative.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall bayu-lengko75-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