Vbkryjetor

Category: packer · Aliases: None known · Sample count (EMBER 2018): 551 · Enrichment: expert-seo · Updated: 2026-06-09

Overview

Worm:Win32/VBKryjetor is a pervasive, Visual Basic-compiled network worm and trojan dropper notorious for rapidly propagating across removable media and local networks.

What is VBKryjetor?
For general users, VBKryjetor causes significant disruption, often hiding legitimate files on USB drives and replacing them with malicious executables. For incident responders, it represents a noisy, classic propagation threat. Because it is compiled in Visual Basic 6 (VB6), it is often bloated and easily decompiled, but its sheer volume and aggressive lateral movement capabilities make it a persistent nuisance in environments with poor USB controls.

Infection Vectors & Threat Hunting
VBKryjetor primarily spreads by copying itself to all connected removable drives, creating an autorun.inf file to automatically execute when the drive is accessed. It also scans local subnets for open SMB shares, attempting to copy itself to vulnerable network locations. Once executed on a host, it copies itself to the %SystemRoot% or %AppData% directories. It establishes persistence via the Registry Run keys and frequently disables critical administrative tools like Task Manager, Registry Editor, and Command Prompt to hinder removal.

Forensic Analysis & Impact
The impact is widespread nuisance, localized network congestion, and potential data loss (via hidden files). EDR platforms frequently detect VBKryjetor based on its unauthorized modifications to HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System. Threat hunters should investigate the sudden appearance of .vbs or randomly named .exe files on the root of network shares and USB drives. The worm also acts as a dropper, frequently downloading secondary adware or spyware payloads.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

TechniqueNameTactic
T1091Replication Through Removable MediaLateral Movement
T1564.001Hide Artifacts: Hidden Files and DirectoriesDefense Evasion
T1562.001Impair Defenses: Disable or Modify ToolsDefense Evasion
T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup FolderPersistence
T1105Ingress Tool TransferCommand and Control

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_VBKRYJETOR {
    meta:
        description = "Detects Vbkryjetor (packer)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "vbkryjetor" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Vbkryjetor Activity
id: ce26bbb7e5a48bdd59cb2b4d66ab5f9e
status: experimental
description: Detects generic indicators of the vbkryjetor malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*vbkryjetor*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Enforce strict Group Policy restrictions disabling the 'AutoRun' and 'AutoPlay' features across the entire domain.
  2. Confiscate and forensically wipe any USB drives or removable media that were connected to the infected endpoint.
  3. Utilize command-line tools to forcefully unhide the legitimate directories on infected network shares and delete the malicious executables.
  4. Deploy a script via Group Policy to re-enable Task Manager, Registry Editor, and Command Prompt on affected endpoints.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not insert a potentially infected USB drive into a clean analysis machine unless AutoRun is strictly disabled and the machine is sandboxed.
  2. Avoid assuming the threat is contained after deleting the USB payload; the worm almost certainly copied itself to local network shares.

References & External Analysis

Related Families (Category: packer)

Explore other malware families in the same category:

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/vbkryjetor.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Replit, StackBlitz, CodeSandbox, and CodePen.