Malicious Code Injection in mulyono-sasag95-ruro Package

mulyono-sasag95-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106027: Malicious code in mulyono-sasag95-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 mulyono-sasag95-ruro package 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 floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability originates from the mulyono-sasag95-ruro package, which contains 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 malicious payload continuously republishes these variants to the npm registry, which can lead to a compromised development environment and increased risk of dependency confusion attacks.

How To Fix

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

npm uninstall mulyono-sasag95-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 mulyono-sasag95-ruro package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The mulyono-sasag95-ruro package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for mulyono-sasag95-ruro →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of your project's dependencies, potentially introducing malicious code that can compromise your application.

You should uninstall the package immediately using the command npm uninstall mulyono-sasag95-ruro and review your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities, making it easier to maintain secure dependencies.

How To Fix

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

npm uninstall mulyono-sasag95-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