Malicious Code Detected in erroroji Package - Security Risk Identified

erroroji Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19799: Malicious code in erroroji (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 erroroji package is an npm library designed for error handling and logging in JavaScript applications. It provides developers with tools to manage and report errors effectively. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the erroroji package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or disrupt application functionality. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall erroroji

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, you can remove the erroroji package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall erroroji.

Conclusion

The erroroji package has been identified to contain malicious code, posing a significant security risk to applications. It is imperative for developers to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for erroroji →

Share this vulnerability

FAQ

The erroroji package is an npm library used for error handling and logging in JavaScript applications.

The malicious code can compromise application security, potentially allowing unauthorized access to sensitive data or executing arbitrary commands.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

It is crucial to check the package repository for a patched version of erroroji. If available, update the package using npm update erroroji.

As a workaround, consider uninstalling the erroroji package until a secure version is released by running npm uninstall erroroji.

How To Fix

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

npm uninstall erroroji

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