Malicious Code Injection in erick-tempe24-ruro Package

erick-tempe24-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102191: Malicious code in erick-tempe24-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 erick-tempe24-ruro package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a broader malicious campaign targeting npm, where packages are designed to inflate developer reputation scores through automated publishing of derivative packages. This specific package has been compromised to include malicious scripts that alter its configuration and behavior.

Vulnerability Detail

The vulnerability in the erick-tempe24-ruro package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior not only compromises the integrity of the package but also pollutes the npm registry with potentially harmful variants. The malicious payload can lead to security risks for applications relying on this package, as it may introduce untrusted code into the software supply chain.

How To Fix

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

npm uninstall erick-tempe24-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 erick-tempe24-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The erick-tempe24-ruro package has been compromised, leading to significant security vulnerabilities. It is crucial for developers to take immediate action by removing the package and monitoring their dependencies for any potential threats. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for erick-tempe24-ruro →

Share this vulnerability

FAQ

The erick-tempe24-ruro package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

This vulnerability can introduce untrusted code into your application, potentially leading to security risks and instability.

You should uninstall the erick-tempe24-ruro package immediately and check for any dependencies that may be affected.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.

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 erick-tempe24-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