Malicious Code Injection in erwin-jamblang38-ruro Package

erwin-jamblang38-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102202: Malicious code in erwin-jamblang38-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 erwin-jamblang38-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 aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, impacting the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being involved in a token reward campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This leads to pollution of the npm registry and can inflate developer reputation scores fraudulently. The malicious payload can also potentially compromise the security of applications relying on this package.

How To Fix

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

npm uninstall erwin-jamblang38-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 erwin-jamblang38-ruro package in your projects. Regularly check your package-lock.json file for any dependencies that may include this package and remove them as necessary.

Conclusion

The erwin-jamblang38-ruro package poses a significant risk due to its malicious code designed to exploit the npm registry. It is essential to remove this package and any dependencies associated with it to maintain the security of your applications. Regular monitoring and using tools like Vulert can help you stay ahead of potential vulnerabilities.

See every vulnerability recorded for erwin-jamblang38-ruro →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign, designed to manipulate the npm registry.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should uninstall the package immediately using 'npm uninstall erwin-jamblang38-ruro' and check for any other affected dependencies.

Yes, the malicious payload can modify your package.json file and publish unauthorized packages, potentially compromising your application's security.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall erwin-jamblang38-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