Malicious Code Detected in ecosystem-iris-eab640-project Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19196: Malicious code in ecosystem-iris-eab640-project (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 ecosystem-iris-eab640-project is an npm package designed for specific functionalities within the JavaScript ecosystem. It is utilized by developers to streamline certain processes in their applications. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the ecosystem-iris-eab640-project package. This code can lead to unauthorized access, data breaches, or other harmful actions that compromise the integrity of applications using this package. The malicious nature of the code was confirmed through security assessments, highlighting the need for immediate action by users of the package.

How To Fix

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

npm uninstall ecosystem-iris-eab640-project

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, users can remove the ecosystem-iris-eab640-project package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall ecosystem-iris-eab640-project'.

Conclusion

The ecosystem-iris-eab640-project package has been found to contain malicious code, necessitating immediate action from users. By updating or removing the package, developers can mitigate the risks associated with this vulnerability. Regular monitoring and updates are essential for maintaining application security.

See every vulnerability recorded for ecosystem-iris-eab640-project →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches or system compromises.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not possible, consider removing the package from your project as a temporary measure.

It is advisable to check for updates regularly, at least once a week, to ensure your application remains secure.

Using a vulnerable package can lead to security breaches, data loss, and damage to your application's reputation.

How To Fix

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

npm uninstall ecosystem-iris-eab640-project

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