Critical Malicious Code Vulnerability in vitor-js Package

vitor-js Updated 17 Dec 2025

Summary

17/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192603: Malicious code in vitor-js (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 vitor-js package is an npm library designed for JavaScript applications, providing various functionalities that developers can leverage in their projects. However, it has been identified as containing malicious code, posing significant security risks to any system where it is installed. This vulnerability can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the vitor-js package. This code can compromise any computer that has the package installed, allowing attackers to gain full control over the system. The ramifications include potential data breaches, unauthorized access to sensitive information, and the ability to manipulate system operations. Users are advised to treat any system with this package as fully compromised, as removing the package may not eliminate all traces of the malicious software.

How To Fix

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

npm uninstall vitor-js

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 are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure that you monitor your system for any unusual activity following the removal.

Conclusion

The vitor-js package has been identified as containing malicious code, posing significant security risks to any systems where it is installed. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of your dependencies is crucial to maintaining a secure environment.

See every vulnerability recorded for vitor-js →

Share this vulnerability

FAQ

You should uninstall the vitor-js package immediately and rotate any sensitive keys or secrets stored on the affected system.

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

Failing to address this vulnerability can lead to unauthorized access, data breaches, and potential manipulation of your system by malicious actors.

No, there is currently no patched version available for vitor-js. The only solution is to remove the package entirely.

While many npm packages are safe, it is essential to monitor and audit your dependencies regularly. Tools like Vulert can help you stay informed about vulnerabilities.

How To Fix

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

npm uninstall vitor-js

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