Malicious Code Injection in eugene-validator-catalyst: A Threat to npm Packages

eugene-validator-catalyst Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102269: Malicious code in eugene-validator-catalyst (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The eugene-validator-catalyst package is part of the npm ecosystem, primarily used for validating transactions in decentralized applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This vulnerability allows attackers to manipulate package metadata and publish harmful derivatives, undermining the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the eugene-validator-catalyst package, which is linked to a broader malicious campaign targeting npm. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of these malicious variants, polluting the npm registry and potentially compromising other applications that rely on these packages. The ramifications include loss of developer reputation, exposure to malicious code, and potential security breaches in applications using these packages.

How To Fix

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

npm uninstall eugene-validator-catalyst

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 remove the eugene-validator-catalyst package from your project by executing: npm uninstall eugene-validator-catalyst. This will prevent any malicious code from executing until a safe version is available.

Conclusion

The eugene-validator-catalyst package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is essential to update or remove this package to protect your applications from potential threats.

See every vulnerability recorded for eugene-validator-catalyst →

Share this vulnerability

FAQ

It is an npm package used for validating transactions in decentralized applications, but it has been compromised with malicious code.

The malicious code can modify your package.json, remove private flags, and publish harmful derivatives, potentially compromising your application's security.

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

As a temporary measure, uninstall the eugene-validator-catalyst package to prevent any malicious code from executing.

Detailed information can be found on the official GitHub repository of the malicious packages or through security advisories related to npm.

How To Fix

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

npm uninstall eugene-validator-catalyst

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