Malicious Code Injection in joni-semur63-ruro: A Threat to npm Ecosystem

joni-semur63-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104699: Malicious code in joni-semur63-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 package joni-semur63-ruro is part of a broader campaign targeting the npm ecosystem, specifically designed to exploit the tea.xyz token reward system. This package, like others in its category, is intended to manipulate developer reputation scores by flooding the npm registry with derivative packages. Its functionality revolves around generating and publishing numerous variants of itself, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in joni-semur63-ruro stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The origin of this vulnerability is linked to a campaign that aims to inflate developer reputation scores through automated publishing scripts. The ramifications include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall joni-semur63-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 measure, avoid using the joni-semur63-ruro package and monitor your dependencies for any malicious activity. You can also use tools like Vulert to check your package-lock.json for vulnerabilities. For example, you can visit the Vulert playground at https://vulert.com/scanner to assess if your application is affected by this vulnerability without needing to sign up.

Conclusion

The joni-semur63-ruro package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate developer reputation scores. It is crucial for developers to be vigilant, remove this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for joni-semur63-ruro →

Share this vulnerability

FAQ

joni-semur63-ruro is an npm package that is part of a malicious campaign to manipulate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

You should uninstall the joni-semur63-ruro package immediately and monitor your project for any unusual behavior.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without any signup.

How To Fix

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

npm uninstall joni-semur63-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