Malicious Code Detected in kresna-oblok3-ruro: npm Package Vulnerability

kresna-oblok3-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104876: Malicious code in kresna-oblok3-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 npm package 'kresna-oblok3-ruro' is part of a series of packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious software.

Vulnerability Detail

The vulnerability in 'kresna-oblok3-ruro' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising the security of applications that depend on it. The malicious code is part of a broader scheme to exploit the npm ecosystem for token rewards, making it a significant threat to developers and users alike.

How To Fix

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

npm uninstall kresna-oblok3-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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json file to lock dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'kresna-oblok3-ruro' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package and utilize monitoring tools like Vulert to safeguard their applications against potential vulnerabilities.

See every vulnerability recorded for kresna-oblok3-ruro →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The malicious code can lead to the proliferation of harmful packages, compromising the security and integrity of your application.

You should uninstall the package immediately and monitor your project for any vulnerabilities using tools like Vulert.

Currently, there is no specific patch for 'kresna-oblok3-ruro', so the best course of action is to uninstall the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

npm uninstall kresna-oblok3-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