Malicious Code Injection in erwin-asinan41-ruro Package

erwin-asinan41-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102197: Malicious code in erwin-asinan41-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 Your last release was probably never penetration tested 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-asinan41-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the erwin-asinan41-ruro package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to a broader campaign that exploits npm for token rewards, posing significant risks to developers and users by compromising package integrity and security.

How To Fix

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

npm uninstall erwin-asinan41-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-asinan41-ruro in its dependencies.

Conclusion

The erwin-asinan41-ruro package contains malicious code that poses significant risks to applications using it. It is crucial to uninstall this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for erwin-asinan41-ruro →

Share this vulnerability

FAQ

The erwin-asinan41-ruro package is an npm package associated with a token reward campaign that automates the generation and publication of derivative packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry with unwanted packages.

You should uninstall the erwin-asinan41-ruro package immediately using 'npm uninstall erwin-asinan41-ruro' to mitigate any risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies, keep packages updated, and use tools like Vulert to monitor for vulnerabilities in your projects.

How To Fix

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

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