Malicious Code Injection in siska-mieaceh83-ruro Package - npm Vulnerability

siska-mieaceh83-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108774: Malicious code in siska-mieaceh83-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The siska-mieaceh83-ruro package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The functionality of this package is compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in the siska-mieaceh83-ruro package originates from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a significant risk of dependency confusion and potential exploitation of applications relying on this package.

How To Fix

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

npm uninstall siska-mieaceh83-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 siska-mieaceh83-ruro package and monitor your dependencies for any malicious activity. Additionally, you can use the following command to uninstall the package: npm uninstall siska-mieaceh83-ruro.

Conclusion

The siska-mieaceh83-ruro package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. Immediate action is required to remove this package and safeguard your applications.

See every vulnerability recorded for siska-mieaceh83-ruro →

Share this vulnerability

FAQ

The siska-mieaceh83-ruro package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

This vulnerability can lead to dependency confusion, allowing attackers to exploit your application by introducing malicious code through compromised packages.

You should immediately remove the siska-mieaceh83-ruro package from your project and monitor your dependencies for any signs of malicious activity.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure you are using reputable packages from trusted sources.

How To Fix

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

npm uninstall siska-mieaceh83-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