Malicious Code Injection in erwin-pisang33-ruro Package

erwin-pisang33-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102220: Malicious code in erwin-pisang33-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 erwin-pisang33-ruro package is part of the npm ecosystem, primarily used for JavaScript development. It is often leveraged in various applications for its functionalities related to token reward systems. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability stems from the package being involved in the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as they may inadvertently expose their applications to further vulnerabilities.

How To Fix

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

npm uninstall erwin-pisang33-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 erwin-pisang33-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package validation in your development environment to prevent the installation of untrusted packages.

Conclusion

The erwin-pisang33-ruro package poses a significant security risk due to its involvement in a malicious campaign that alters package metadata. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for erwin-pisang33-ruro →

Share this vulnerability

FAQ

The erwin-pisang33-ruro package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata.

This vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

You should uninstall the erwin-pisang33-ruro package immediately and check your project for any other potentially compromised packages.

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

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

How To Fix

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

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