Malicious Code Injection in ethanjackson Package: npm Vulnerability Overview

ethanjackson Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171176: Malicious code in ethanjackson (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 ethanjackson package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been implicated in a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability stems from the ethanjackson package being part of a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is indicative of a broader strategy to manipulate the npm ecosystem for token rewards, leading to potential security risks such as unauthorized access and code injection. The malicious payload continuously republishes variants, further polluting the npm registry and compromising the integrity of the packages available to developers.

How To Fix

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

npm uninstall ethanjackson

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 avoid using the ethanjackson package and replace it with a trusted alternative. Additionally, you can monitor your project for any unauthorized changes to the package.json file.

Conclusion

The ethanjackson package poses a significant risk due to its involvement in a malicious campaign that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for ethanjackson →

Share this vulnerability

FAQ

The ethanjackson package is an npm package that has been linked to a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to unauthorized modifications of your project's dependencies, potentially introducing malicious code.

You should remove the ethanjackson package from your project immediately and check for any unauthorized changes.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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 ethanjackson

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