Malicious Code Injection in arif-mendoan31-ruro Package

arif-mendoan31-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99573: Malicious code in arif-mendoan31-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The arif-mendoan31-ruro package is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the arif-mendoan31-ruro package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of variants. This not only pollutes the npm registry but also compromises the security of applications that may inadvertently depend on these malicious packages. The ramifications include potential exposure to further attacks and degradation of the npm ecosystem.

How To Fix

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

npm uninstall arif-mendoan31-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 arif-mendoan31-ruro package and any other packages that may be part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit or Vulert to identify and mitigate vulnerabilities.

Conclusion

The arif-mendoan31-ruro package poses a significant security risk due to its malicious code designed to manipulate package configurations and pollute the npm registry. It is essential to remove this package from your dependencies and monitor your project for vulnerabilities using tools like Vulert.

See every vulnerability recorded for arif-mendoan31-ruro →

Share this vulnerability

FAQ

The arif-mendoan31-ruro package is an npm package associated with a token reward campaign that automates the generation of derivative packages.

The malicious code can compromise your application's security by modifying package configurations and introducing potentially harmful dependencies.

You should immediately uninstall the arif-mendoan31-ruro package and check your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

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

How To Fix

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

npm uninstall arif-mendoan31-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