Critical Malicious Code Vulnerability in @varsityvibe/utils Package

@varsityvibe/utils Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191061: Malicious code in @varsityvibe/utils (npm). Affects @varsityvibe/utils versions 5.0.6. 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 @varsityvibe/utils package is an npm library designed to provide utility functions for various applications. It is commonly used in JavaScript projects to streamline development processes. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from a malicious code injection within version 5.0.6 of the @varsityvibe/utils package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The implications are severe, as the malicious actor may gain complete control over the affected system, making it imperative for users to act swiftly.

How To Fix

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

npm uninstall @varsityvibe/utils

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 workaround, if you still need similar functionality, consider using alternative utility packages that are known to be secure. Always verify the integrity of packages before installation.

Conclusion

The discovery of malicious code in the @varsityvibe/utils package highlights the importance of vigilance in software dependency management. Users must take immediate action to remove the compromised package and secure their systems. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @varsityvibe/utils →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall @varsityvibe/utils' and rotate any sensitive information that may have been compromised.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.

To prevent similar issues, always review package dependencies, use trusted sources, and regularly monitor your projects for vulnerabilities.

Vulert is a tool that monitors open-source vulnerabilities in your software using just the package-lock.json file. It provides real-time alerts for any vulnerabilities detected.

How To Fix

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

npm uninstall @varsityvibe/utils

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