Malicious Code Injection in ida-sambel87-ruro Package

ida-sambel87-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103910: Malicious code in ida-sambel87-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 ida-sambel87-ruro package is part of the npm ecosystem and is associated with 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. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the ida-sambel87-ruro package. This code 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. The ramifications include potential pollution of the npm registry and exploitation of developer reputation systems, which can undermine trust in the ecosystem.

How To Fix

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

npm uninstall ida-sambel87-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, consider using a package-lock.json file to monitor your dependencies. This file can help you identify and manage vulnerable packages. Additionally, you can use tools like Vulert to check if your application is affected by this vulnerability without requiring code access or installation. You can visit the Vulert playground at https://vulert.com/scanner to perform this check.

Conclusion

The ida-sambel87-ruro package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your software.

See every vulnerability recorded for ida-sambel87-ruro →

Share this vulnerability

FAQ

The ida-sambel87-ruro package is an npm package involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated package publishing.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to the pollution of the npm registry and potential security risks.

You should uninstall the ida-sambel87-ruro package immediately using the command npm uninstall ida-sambel87-ruro and check for any dependencies that may be affected.

Yes, you can use tools like Vulert, which monitors your package-lock.json file 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 ida-sambel87-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