Active threat familyWindowsCredential theft
Malware Intelligence

CryptBot

CryptBot is a typical infostealer that collects browser passwords, cookies, card details and crypto wallets and takes screenshots. All data is placed in a single ZIP archive and uploaded to the C2.

Activity map

BleepingComputerBleepingComputer

Activity mapDownloadDownloadExtractionExecutionPackagingExfiltrationUnlicensedsoftware siteCrack sitesFake download siteFake KMSPicoZIPPassword-protectedarchiveEXEInstallationCryptBotInfostealerData collection12 targetsLog archiveC2 server
Executable payloadFile
Malicious payloadCryptBot · Infostealer

CryptBot is a typical infostealer that collects browser passwords, cookies, card details and crypto wallets and takes screenshots. All data is placed in a single ZIP archive and uploaded to the C2.

Environment information

  • Operating system
  • Hardware
  • IP and location
  • Installed software
  • Screenshot
  • Desktop files

Credentials and application data

  • Saved passwords
  • Session cookies
  • Saved cards
  • Exodus
  • Electrum
  • Atomic Wallet
  • MetaMask
  • Coinomi
Dark Radar infection records
1,222,383
Latest infection record
31 August 2026
Malware type
Infostealer
First seen
2019
01

Overview

Ranks 7 of 52 families in Dark Radar data, with 1,222,383 infection records.

02

Origin and evolution

  1. 2020Distributed through code hosting services such as Bitbucket.Malpedia (Fraunhofer FKIE)
  2. 2021Wallet theft through fake KMSPico activation tools.BleepingComputer
  3. 2022A renewed version spread from unlicensed software sites.BleepingComputer
03

Technical profile

Malware typeInfostealer
Target operating systemWindows
Primary purposeCrypto asset and identity theft
Threat categoryCredential theft
Programming languageC++
Distribution modelPay-per-install (PPI) distribution networks
First seen2019
Infected systemsWindows 10 63%, Windows 8.1 5%
Public source confidenceHigh
04

Targeted applications

12 applications4 categories
05

Data collection

Credentials

  • Browser passwords86.5%Verified
  • Session cookies93%Verified
  • Refreshing expired sessions—
  • Autofill—
  • macOS Keychain—
  • 2FA and password managers—

Financial

  • Saved cards3.5%Verified
  • Desktop crypto walletsVerified
  • Wallet extensionsVerified
  • Clipboard address replacement—

System

  • File collection9.5%Dark Radar observation
  • Screenshot62.5%Verified
  • System inventory99.5%Verified

Behavior

  • Additional payload download—
  • Persistence—
  • Anti-analysisVersion-dependent
06

File system

User profile (%USERPROFILE%)
File details are in Dark Radar IntelligenceOpen in Intelligence
07

System components

  • System information
  • Screenshot
08

How it works

  1. 1Infection

    • Unlicensed software and "crack" sites.
    • Fake activation tools.

    Breaking point: Email attachments, sponsored ad links and unlicensed software downloads are blocked at the email and web gateway.

  2. 2Execution and evasion

    • The packed payload is unpacked in memory.
    Dark Radar observation

    The payload ran from the Program Files folder (latest 200 logs, 58.4%).

    The payload ran from the temporary folder (latest 200 logs, 24.8%).

    Ran from the dd.exe file in the Windows folder (latest 200 logs, 16.8%).

    T1204.002User Execution: Malicious FileT1070.004File DeletionT1027Obfuscated Files or Information

    Breaking point: Unsigned files running from user folders and injections into .NET tools are stopped by application control and EDR.

  3. 3Discovery

    • System information and screenshot.
    Dark Radar observation

    Infected systems: Windows 10 63%, Windows 8.1 5%, Windows 7 4.5%.

    T1082System Information Discovery

    Breaking point: Bulk system and security software queries from a short-lived process trigger an EDR alert.

  4. 4Data collection

    • Browser and wallet data is collected in a folder.
    Dark Radar observation

    Data found in the latest 200 logs: password file 86.5%, cookies 93%, cards 3.5%, wallets 0.5%.

    T1555.003Credentials from Web BrowsersT1539Steal Web Session CookieT1005Data from Local SystemT1113Screen CaptureT1560Archive Collected Data

    Breaking point: A process other than the browser reading browser profile files is blocked or triggers an alert.

  5. 5Exfiltration and C2

    • The ZIP archive is uploaded to the C2; local copies are then deleted.
    T1071.001Web ProtocolsT1041Exfiltration Over C2 Channel

    Breaking point: Traffic to newly registered domains, direct IP addresses and non-standard ports is blocked.

09

Network communication

This section is in Dark Radar IntelligenceOpen in Intelligence
10

MITRE ATT&CK

Execution
Credential Access
Discovery
Collection
Command and Control
Exfiltration
Defense Evasion
11

IOCs and detection

This section is in Dark Radar IntelligenceOpen in Intelligence
12

Risk and impact

  • Stolen session cookies are enough to take over cloud, email and SaaS sessions without a password or multi-factor authentication prompt.
  • Corporate passwords saved on personal devices also leak through infections outside the corporate network; these logs are sold to initial access brokers.
  • Log archives are reshared for years; as long as the password is not changed, the same credential can be used again and again.
  • Compromised email, messaging and social media accounts become the next link in phishing and malware distribution.
13

Defense

  • When an infection is detected, revoke not only the password but all related sessions and access tokens.
  • Turn off password saving in the browser through corporate policy; use a corporate password manager.
  • Move to phishing-resistant multi-factor authentication (FIDO2/passkey); bind sessions to the device.
  • Block setup files downloaded from unlicensed software, game cheats and sponsored search results.
  • Monitor flows where the user runs a command by pasting it into the Run dialog or terminal (ClickFix) with endpoint rules.
  • Continuously monitor your corporate domains and employee email addresses in stealer logs with Dark Radar.
14

Learning center

How does this malware spread?
  • Unlicensed software and "crack" sites.
  • Fake activation tools.
  • The payload ran from the Program Files folder (latest 200 logs, 58.4%).
  • The payload ran from the temporary folder (latest 200 logs, 24.8%).
How can its presence on a system be detected?
  • Sign-ins to accounts from an unrecognized country or device.
  • A new infostealer log in Dark Radar for your corporate domain or an employee email address.
Which Windows artifacts should be examined?
  • Prefetch (C:\Windows\Prefetch) — shows that a short-lived payload ran.
  • Amcache.hve and ShimCache — path and hash of the executed file.
  • Downloads folder and Zone.Identifier stream — the address the file was downloaded from.
  • Browser history — the fake download page or fake CAPTCHA address.
  • RunMRU registry key — commands pasted into the Run dialog.
  • Randomly named folders and DLLs under %TEMP% and %LOCALAPPDATA%.
Which log records matter?
  • Sysmon Event 1 / Security 4688Process creation: unsigned processes starting from Temp and Downloads folders, mshta, powershell -enc chains.
  • Sysmon Olay 11 / 23File creation and deletion: self-deleting payloads, DLLs dropped under Temp.
  • Sysmon Olay 3 / 22Network connection and DNS query: to newly registered domains, C2 resolution via Telegram, Steam or Pastebin.
  • Object access auditing (4663)A process other than the browser reading Login Data, Cookies and Local State files.
  • PowerShell 4104Script block logging: obfuscated downloader commands.
  • Identity provider sign-in logsSessions after the infection from a different country and device, without a multi-factor authentication prompt.
Which MITRE techniques is it associated with?
T1204.002User Execution: Malicious FileT1555.003Credentials from Web BrowsersT1539Steal Web Session CookieT1082System Information DiscoveryT1005Data from Local SystemT1071.001Web ProtocolsT1041Exfiltration Over C2 ChannelT1113Screen CaptureT1560Archive Collected DataT1070.004File DeletionT1027Obfuscated Files or Information
How should a SOC analyst respond?
  1. Isolate the device from the network; do not reinstall it before taking memory and disk images.
  2. Determine the infection date; list all accounts that were signed in on the device after that date.
  3. Change the passwords of these accounts, revoke their sessions and access tokens, and re-enroll multi-factor authentication devices.
  4. Search identity provider and SaaS logs for new country, device and token usage after the infection.
  5. If a recovery phrase or wallet file was exposed, move the assets to a new wallet.
  6. Find the initial access path (email, ad, unlicensed software, fake CAPTCHA) and check other users who used the same path.
  7. Reinstall the device from a clean image.
15

Sources

Related families

RedLine StealerVidarCompare

Related terms

JoinerWallet theft
From the Essential plan

Infostealer Detection

See your firm's attack surface on one screen: how many findings, at which severity, on which domain.

View productCompare plans