Malicious Code Injection in erwin-pisang81-ruro: A Threat to npm Ecosystem

erwin-pisang81-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102221: Malicious code in erwin-pisang81-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 package erwin-pisang81-ruro is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, notorious for flooding npm with malicious packages. Its primary function appears to be related to generating and publishing derivative packages, which can inflate developer reputation scores for token rewards. However, this functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in erwin-pisang81-ruro stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially compromising other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages.

How To Fix

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

npm uninstall erwin-pisang81-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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include erwin-pisang81-ruro in its dependencies. You can also utilize Vulert to monitor your project for vulnerabilities in real-time without requiring code access or installation.

Conclusion

The erwin-pisang81-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior, which can compromise project integrity and pollute the npm registry. It is crucial to remove this package and monitor for updates to safeguard your applications.

See every vulnerability recorded for erwin-pisang81-ruro →

Share this vulnerability

FAQ

erwin-pisang81-ruro is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially affecting other packages and compromising the integrity of your project.

You should remove the erwin-pisang81-ruro package from your project and monitor for any updates or patches that may be released.

Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file, ensuring you are alerted to any issues.

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

How To Fix

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

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