Malicious Code Injection in siska-esdoger30-ruro Package

siska-esdoger30-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108756: Malicious code in siska-esdoger30-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 siska-esdoger30-ruro package is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate npm's registry by creating and publishing numerous derivative packages with randomized names, ultimately aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability in the siska-esdoger30-ruro package originates from its inclusion in a campaign that floods the npm registry with malicious packages. The payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall siska-esdoger30-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 workaround, you can avoid using the siska-esdoger30-ruro package altogether. If it is already in your project, remove it by running: npm uninstall siska-esdoger30-ruro. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The siska-esdoger30-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 from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive can help mitigate the risks associated with open-source dependencies.

See every vulnerability recorded for siska-esdoger30-ruro →

Share this vulnerability

FAQ

The siska-esdoger30-ruro package is an npm package that has been identified as malicious, designed to manipulate the npm registry.

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

If you have installed the siska-esdoger30-ruro package, you should uninstall it immediately and monitor your project for any unusual behavior.

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

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories.

How To Fix

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

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