Critical Malicious Code Vulnerability in @markvivanco/app-version-checker

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190818: Malicious code in @markvivanco/app-version-checker (npm). Affects @markvivanco/app-version-checker versions 1.0.1 – 1.0.2. 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 @markvivanco/app-version-checker is an npm package designed to assist developers in checking and managing application versions. It is commonly used in JavaScript projects to ensure that the correct versions of dependencies are being utilized. However, this package has been identified as containing malicious code, posing significant security risks to systems that have it installed.

Vulnerability Detail

This vulnerability originates from the package being compromised with embedded malicious code. Any system running this package is considered fully compromised, allowing potential attackers to gain unauthorized access to sensitive information, including secrets and keys stored on the affected computer. The malicious nature of the code means that simply removing the package may not eliminate all traces of the attack, as full control of the system may have been relinquished to an external entity.

How To Fix

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

npm uninstall @markvivanco/app-version-checker

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 need similar functionality, consider using alternative packages that provide version checking without the associated risks. Always verify the integrity and reputation of packages before installation.

Conclusion

The discovery of malicious code in the @markvivanco/app-version-checker npm package poses a serious threat to users. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for vulnerabilities in the future.

See every vulnerability recorded for @markvivanco/app-version-checker →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall @markvivanco/app-version-checker and rotate any sensitive information stored on the affected system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Leaving this package installed can lead to unauthorized access to sensitive data, potential data breaches, and complete compromise of your system.

After removing the package, it is essential to rotate all secrets and keys stored on the compromised system. Additionally, conduct a thorough security audit to identify any other potential vulnerabilities.

Yes, consider using other well-reviewed and secure packages that offer similar functionality without the associated risks. Always check the package's reputation before installation.

How To Fix

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

npm uninstall @markvivanco/app-version-checker

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