Malicious Code Injection in sari-kue93-ruro Package

sari-kue93-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108362: Malicious code in sari-kue93-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 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 sari-kue93-ruro package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that modify package metadata and republish variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the sari-kue93-ruro package. This code is designed to remove private flags from the package.json file, alter version numbers, and create random package names, primarily themed around Indonesian culture. The continuous republishing of these variants can lead to significant pollution of the npm registry, affecting developers and users relying on legitimate packages. The malicious payload can compromise the integrity of applications that depend on this package, potentially leading to security risks and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall sari-kue93-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 sari-kue93-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The sari-kue93-ruro package has been identified as containing malicious code that poses a significant risk to developers and users within the npm ecosystem. Immediate action is required to remove the package and monitor for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for sari-kue93-ruro →

Share this vulnerability

FAQ

The sari-kue93-ruro package is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The malicious code modifies package metadata and republish variants, potentially leading to security risks and pollution of the npm registry.

You should uninstall the sari-kue93-ruro package immediately using 'npm uninstall sari-kue93-ruro' and look for alternative packages.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall sari-kue93-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