Malicious Code Injection in jaja-sroto77-ruro Package

jaja-sroto77-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104519: Malicious code in jaja-sroto77-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The jaja-sroto77-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automatic publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and republishes variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the jaja-sroto77-ruro package, which includes scripts that automatically generate and publish derivative packages with randomized names. This malicious behavior alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently contribute to the pollution of the npm registry and compromise their projects.

How To Fix

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

npm uninstall jaja-sroto77-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 jaja-sroto77-ruro package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The jaja-sroto77-ruro package contains malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for jaja-sroto77-ruro →

Share this vulnerability

FAQ

The jaja-sroto77-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise your project's security if you inadvertently install malicious packages.

You should uninstall the jaja-sroto77-ruro package immediately using the command: npm uninstall jaja-sroto77-ruro.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall jaja-sroto77-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