Malicious Code Injection in siska-tahu33-ruro Package: npm Vulnerability Overview

siska-tahu33-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108787: Malicious code in siska-tahu33-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The siska-tahu33-ruro package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. The package is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability in the siska-tahu33-ruro package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, leading to a polluted npm registry. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as they may contain harmful code or lead to reputation damage.

How To Fix

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

npm uninstall siska-tahu33-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-tahu33-ruro package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate risks.

Conclusion

The siska-tahu33-ruro package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to remove this package from their projects and to adopt best practices for dependency management to safeguard against similar vulnerabilities.

See every vulnerability recorded for siska-tahu33-ruro →

Share this vulnerability

FAQ

siska-tahu33-ruro is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

You should immediately uninstall the siska-tahu33-ruro package using the command npm uninstall siska-tahu33-ruro.

Regularly audit your dependencies, use trusted packages, and keep your packages updated to their latest versions.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

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