Malicious Code Injection in emmamartin Package: npm Vulnerability Overview

emmamartin Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171159: Malicious code in emmamartin (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The emmamartin package is part of the npm ecosystem, primarily used for JavaScript development. It is often utilized in various applications to manage dependencies and streamline development processes. However, this package has been identified as part of a malicious campaign that exploits npm's publishing system, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the emmamartin package stems from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to unauthorized access and manipulation of developer reputation scores.

How To Fix

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

npm uninstall emmamartin

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 emmamartin package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The emmamartin package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your application.

See every vulnerability recorded for emmamartin →

Share this vulnerability

FAQ

The emmamartin package is an npm package used in JavaScript development, but it has been identified as malicious due to its involvement in a token reward scheme.

The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your application's integrity and security.

You should remove the emmamartin package from your project immediately and monitor for any updates or patches.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall emmamartin

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