Malicious Code Injection in agus-ketoprak32-ruro Package

agus-ketoprak32-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99297: Malicious code in agus-ketoprak32-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 agus-ketoprak32-ruro package is an npm module that is part of a broader token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate certain functionalities within the npm ecosystem, but it has been compromised to include malicious scripts that can adversely affect developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the agus-ketoprak32-ruro package. This code is part of a campaign that floods the npm registry with derivative packages, modifying the package.json file to remove private flags, altering version numbers, and generating random package names. The ramifications include the potential for developers to unknowingly publish compromised packages, leading to a polluted npm registry and inflated reputation scores for malicious actors.

How To Fix

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

npm uninstall agus-ketoprak32-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 affected package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The agus-ketoprak32-ruro package has been identified as containing malicious code that poses significant risks to developers and the npm registry. It is crucial to take immediate action by uninstalling the package and monitoring your project for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for agus-ketoprak32-ruro →

Share this vulnerability

FAQ

The agus-ketoprak32-ruro package is an npm module that is part of a token reward campaign, but it has been compromised to include malicious code.

The malicious code can modify your package.json file, remove private flags, and publish compromised packages, potentially harming your project's integrity.

You should uninstall the package immediately using npm uninstall agus-ketoprak32-ruro and check for other compromised packages in your project.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application.

Yes, consider looking for alternative npm packages that provide similar functionalities without the associated risks of malicious code.

How To Fix

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

npm uninstall agus-ketoprak32-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