Malicious Code Injection in oktafian-bakso96-ruro: A Threat to npm Packages

oktafian-bakso96-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106663: Malicious code in oktafian-bakso96-ruro (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 'oktafian-bakso96-ruro' is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant security risk due to the malicious code embedded within.

Vulnerability Detail

The vulnerability in 'oktafian-bakso96-ruro' originates 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 malicious payload allows the package to continuously republish variants, effectively polluting the npm registry and potentially compromising other packages and applications that depend on it. The ramifications include unauthorized access to sensitive data, disruption of service, and damage to the reputation of developers using affected packages.

How To Fix

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

npm uninstall oktafian-bakso96-ruro

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

Conclusion

The 'oktafian-bakso96-ruro' package poses a significant security threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to remove this package from their projects and to adopt best practices for monitoring and managing dependencies to safeguard their applications.

See every vulnerability recorded for oktafian-bakso96-ruro →

Share this vulnerability

FAQ

The main risk is the malicious code that modifies package.json, allowing for unauthorized republishing of variants and potential compromise of other packages.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without signup.

You should uninstall the package immediately using 'npm uninstall oktafian-bakso96-ruro' and review your project for any unauthorized changes.

Yes, consider searching for other npm packages that offer similar functionality but are known to be secure and reputable.

Regularly update your dependencies, use tools like Vulert for real-time monitoring, and review package sources before installation.

How To Fix

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

npm uninstall oktafian-bakso96-ruro

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