Beyondkeylogger

Category: infostealer · Aliases: PWS:Win32/Beyondkeylogger, PWS.Win32.Beyondkeylogger, Win32/Beyondkeylogger · Sample count (EMBER 2018): 8 · Enrichment: curated_sourced · Updated: 2026-10-16
Category: InfostealerStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceActor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Beyondkeylogger (classified in antivirus detection telemetry under designations including PWS:Win32/Beyondkeylogger, PWS.Win32.Beyondkeylogger, and Win32/Beyondkeylogger) is a dedicated information theft malware engineered to harvest stored credentials, browser session cookies, cryptocurrency wallets, and keystrokes.

Table of Contents

Overview

Beyondkeylogger (classified in antivirus detection telemetry under designations including PWS:Win32/Beyondkeylogger, PWS.Win32.Beyondkeylogger, and Win32/Beyondkeylogger) is a dedicated information theft malware engineered to harvest stored credentials, browser session cookies, cryptocurrency wallets, and keystrokes. Disseminated across enterprise networks and consumer workstations via social engineering, phishing attachments, malicious drive-by downloads, or weaponized software cracks, Beyondkeylogger executes an initial reconnaissance phase upon system ingress. The binary evaluates host privileges, detects active hypervisors and sandbox environments to evade behavioral analysis, and establishes resilient autostart persistence by configuring registry keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run or registering background Windows services. Operational mechanics characteristic of this family include credential database extraction, API hooking, system discovery, and encrypted C2 exfiltration. Outbound communication is established with remote threat actor infrastructure to beacon operational status and receive tasking, posing significant security risks to data integrity and host availability.

Known aliases

Threat reports may refer to this family under multiple names:

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-NDFNetwork Data FilteringIsolateT1048.003Inspect non-standard port traffic and block unauthorized ICMP or DNS tunneling protocols at the network perimeter.
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-CACClipboard Access ControlIsolateT1115Isolate virtual desktop infrastructure (VDI) clipboards and alert on rapid background clipboard querying by non-foreground processes.

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_BEYONDKEYLOGGER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Beyondkeylogger"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "beyondkeylogger" ascii wide nocase
        $s2 = "pws:win32/beyondkeylogger" ascii wide nocase
        $s3 = "pws.win32.beyondkeylogger" ascii wide nocase
        $s4 = "win32/beyondkeylogger" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Beyondkeylogger (Infostealer) Execution & Triage
id: f351c4c4-a318-55eb-a648-f430ac8f060c
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Beyondkeylogger malware family. Detects browser credential database harvesting,
  master key queries, and DPAPI extraction routines typical of modern infostealers.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/beyondkeylogger
- https://malware-families-catalog.systemhelpdesk.com/defensive/infostealer-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.infostealer
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1555
- attack.t1056_001
- attack.t1114
- attack.t1041
- attack.t1082
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \rundll32.exe
    CommandLine|contains:
    - \Google\Chrome\User Data\Default\Login Data
    - \AppData\Roaming\Mozilla\Firefox\Profiles
    - \AppData\Local\Microsoft\Edge\User Data
    - vaultcmd.exe /list
    - dpapi
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_BEYONDKEYLOGGER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Beyondkeylogger tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "beyondkeylogger" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Instantly isolate the endpoint to halt the exfiltration of the captured keystrokes and screenshots.
  2. Enforce a mandatory, immediate password reset for *every* account the user has accessed from that machine, prioritizing domain credentials and VPN access.
  3. Do not simply delete the executable; commercial keyloggers often use rootkit-like techniques to hide. Use an enterprise EDR solution to forcefully terminate the hooking service and clean the registry.
  4. Perform a forensic review to determine how the software was installed (checking for unauthorized physical access or phishing vectors).

What to Avoid

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

  1. Do not assume only the local user's data was compromised; if an administrator logged into the infected machine, their credentials were also logged.
  2. Avoid leaving the endpoint on the network while investigating, as the keylogger will continue to transmit data in real-time.

References & External Analysis

Frequently Asked Questions

What is PWS:Win32/Beyondkeylogger?

Beyondkeylogger is a infostealer threat designed to infiltrate Windows systems and execute unauthorized operations without user consent.

How does Beyondkeylogger compromise target systems?

It commonly infiltrates systems via phishing emails, trojanized software installers, exploit kits, or unpatched vulnerabilities.

What persistence mechanisms does Beyondkeylogger utilize?

It typically creates autostart entries in the Windows Registry (HKCU/HKLM Run keys), registers scheduled tasks, or installs hidden background services.

What risks does Beyondkeylogger pose to an enterprise?

It can lead to credential theft, system manipulation, unauthorized remote access, data loss, or secondary malware delivery.

How can administrators detect and eliminate Beyondkeylogger?

Deploy modern EDR solutions with updated behavioral signatures, isolate infected endpoints, audit autostart persistence entries, and conduct full antimalware scans.

How do I remove Beyondkeylogger from Windows?

Manual removal of Beyondkeylogger is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

What are the main symptoms of a Beyondkeylogger infection?

Symptoms of Beyondkeylogger can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Infostealers

Want to prevent Beyondkeylogger and similar threats from compromising your organization? Read our comprehensive defensive guide: InfoStealer Protection & Remediation.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/beyondkeylogger.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, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.