Malicious Code Injection in emilyporter Package: A Threat to npm Users

emilyporter Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171151: Malicious code in emilyporter (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The emilyporter package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the emilyporter package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically generate and publish derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry and compromise the integrity of the ecosystem.

How To Fix

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

npm uninstall emilyporter

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 emilyporter package and monitor your project for any dependencies that may inadvertently include it. Regularly check your package-lock.json file for any unexpected changes or additions.

Conclusion

The emilyporter package poses a significant security risk due to its malicious code designed to exploit npm's publishing capabilities. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for emilyporter →

Share this vulnerability

FAQ

The emilyporter package is a JavaScript package available on npm, which has been identified as part of a malicious campaign targeting the npm ecosystem.

The malicious code can modify your package.json file, remove private flags, and publish unauthorized versions of your package, potentially compromising your project's integrity.

If you have installed the emilyporter package, you should uninstall it immediately using the command 'npm uninstall emilyporter'.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.

There is no patch available for the emilyporter package, as it is recommended to remove it entirely from your project.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall emilyporter

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