Malicious Code Injection in oktafian-lapis31-breki: A Threat to npm Ecosystem

oktafian-lapis31-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74834: Malicious code in oktafian-lapis31-breki (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'oktafian-lapis31-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in 'oktafian-lapis31-breki' originates from its association with the tea.xyz token reward campaign. The malicious code embedded within the package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only affects the affected package but also leads to the continuous republishing of variants, which can clutter the npm registry and potentially introduce security risks to other packages that depend on it.

How To Fix

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

npm uninstall oktafian-lapis31-breki

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 remove the affected package from your project by executing the following command: npm uninstall oktafian-lapis31-breki. This will help prevent any malicious code execution until a fix is available.

Conclusion

The 'oktafian-lapis31-breki' package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is essential to take immediate action by updating or removing the package to safeguard your applications from potential threats.

See every vulnerability recorded for oktafian-lapis31-breki →

Share this vulnerability

FAQ

The vulnerability can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially introducing 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.

If no patched version is available, it is recommended to remove the package from your project to mitigate any risks associated with the vulnerability.

Signs of compromise may include unexpected behavior in your application, such as unauthorized package installations or modifications to your package.json file.

The malicious code can lead to a proliferation of derivative packages that clutter the npm registry, making it difficult for developers to find legitimate packages and potentially introducing vulnerabilities into their projects.

How To Fix

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

npm uninstall oktafian-lapis31-breki

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