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

evieharrison Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171180: Malicious code in evieharrison (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The evieharrison package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. The primary functionality of evieharrison is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata and flood the npm registry with derivative packages.

Vulnerability Detail

The vulnerability in the evieharrison package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with numerous unwanted packages, potentially leading to security risks for users who inadvertently install these derivatives.

How To Fix

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

npm uninstall evieharrison

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 evieharrison package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.

Conclusion

The evieharrison package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. Users are advised to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for evieharrison →

Share this vulnerability

FAQ

The evieharrison package is an npm package that has been linked to a malicious campaign aimed at exploiting npm's publishing system.

The malicious code modifies your package.json file and floods the npm registry with unwanted packages, which can lead to security vulnerabilities in your project.

You should remove the evieharrison package from your project immediately and check for any other affected packages.

You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

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 evieharrison

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