Malicious Code Detected in backupvbs Package - Immediate Action Required

backupvbs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15326: Malicious code in backupvbs (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The backupvbs package is an npm library designed for creating backups of Visual Basic scripts. It is utilized by developers to automate the backup process, ensuring that critical scripts are preserved. However, this package has been identified to contain malicious code, posing significant risks to users who rely on it for their development needs.

Vulnerability Detail

The vulnerability in the backupvbs package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall backupvbs

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, users can manually back up their Visual Basic scripts without using the backupvbs package. This can be done by copying the script files to a secure location using standard file management commands in the terminal or file explorer.

Conclusion

The backupvbs package has been identified as containing malicious code that poses a significant risk to users. Immediate action is required to remove the package and prevent potential security breaches. Users are encouraged to utilize alternative methods for backing up their Visual Basic scripts and to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for backupvbs →

Share this vulnerability

FAQ

The backupvbs package is an npm library used for automating the backup of Visual Basic scripts.

The malicious code can lead to unauthorized access and potential data breaches within applications that use the package.

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

You should remove the backupvbs package from your project and consider using a secure alternative for your backup needs.

Currently, there is no patched version available. The best course of action is to remove the package.

How To Fix

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

npm uninstall backupvbs

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