Malicious Code Injection in ogi-toge53-ruro: A Threat to npm Packages

ogi-toge53-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106608: Malicious code in ogi-toge53-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 'ogi-toge53-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with randomized names. The primary functionality of this package is to participate in the tea.xyz token reward campaign, which has led to its vulnerability to malicious code injection.

Vulnerability Detail

The vulnerability in 'ogi-toge53-ruro' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to reputation inflation for developers. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, potentially leading to security breaches in applications that rely on them.

How To Fix

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

npm uninstall ogi-toge53-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 temporarily avoid using the 'ogi-toge53-ruro' package in your project until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'ogi-toge53-ruro' package poses a significant security risk due to its malicious code injection. It is crucial for developers to be aware of such vulnerabilities, remove affected packages, and utilize tools like Vulert to monitor their applications for potential threats. Staying informed and proactive can help maintain the security of your software projects.

See every vulnerability recorded for ogi-toge53-ruro →

Share this vulnerability

FAQ

The impact includes potential security breaches due to the injection of malicious code and the pollution of the npm registry with compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed the package, it is advisable to remove it immediately and check for any other dependencies that may have been affected.

Yes, consider using other reputable npm packages that offer similar functionality without the associated risks of malicious code.

Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall ogi-toge53-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