Malicious Code in hyvee.com (npm)

hyvee.com Updated 02 Oct 2025

Summary

09/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8318: Malicious code in hyvee.com (npm). Affects hyvee.com versions 3.3.3. 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 package 'hyvee.com' is an npm package that is used for unknown functionality. It has been identified as malicious by the OpenSSF Package Analysis project. The package version 3.3.3 is affected by this vulnerability.

Vulnerability Detail

The 'hyvee.com' package communicates with a domain associated with malicious activity and executes one or more commands associated with malicious behavior. This can lead to unauthorized access, data breaches, or other malicious activities.

How To Fix

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

npm uninstall hyvee.com

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

There is no known workaround for this vulnerability. It is crucial to remove the 'hyvee.com' package and replace it with a secure alternative.

Conclusion

The 'hyvee.com' package version 3.3.3 has been identified as malicious due to its communication with a domain associated with malicious activity and execution of commands associated with malicious behavior. It is crucial to remove this package from your project and replace it with a trusted alternative to mitigate the risk of unauthorized access and data breaches. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for hyvee.com →

Share this vulnerability

FAQ

This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

You can use Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.

Yes, the fix for this vulnerability is to remove the 'hyvee.com' package from your project and replace it with a trusted alternative.

No, there is no known workaround for this vulnerability. It is essential to remove the 'hyvee.com' package to mitigate the risk.

For further support on vulnerability remediation, you can contact info@devnack.com.

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 hyvee.com

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