Active threat familyWindowsCredential theft
Malware Intelligence

PureLogs

PureLogs is a .NET-based infostealer developed by PureCoder, who is also the author of PureRAT and PureMiner. It collects browser logins, cards, cookies, wallets, and VPN and messaging credentials.

Activity map

Activity mapDownloadDownloadIn memoryPackagingExfiltrationPhishing emailRequest for quotationJSScript attachmentZIPArchive attachmentDownload from aremote serverPNG imagePNGSteganography.NET loaderIn memoryPureLogsInfostealerData collection27 targetsLog archiveC2 server
Executable payloadFile
Malicious payloadPureLogs · Infostealer

PureLogs is a .NET-based infostealer developed by PureCoder, who is also the author of PureRAT and PureMiner. It collects browser logins, cards, cookies, wallets, and VPN and messaging credentials.

Environment information

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

Credentials and application data

  • Saved passwords
  • Session cookies
  • Session refresh data
  • Autofill
  • Saved cards
  • Steam
  • Microsoft Outlook
  • MetaMask
  • Phantom
  • Coinbase Wallet
  • Trust Wallet
  • Binance Wallet
  • TronLink
  • Exodus
Dark Radar infection records
831,640
Latest infection record
28 October 2026
Malware type
Infostealer
First seen
2022
01

Overview

Ranks 8 of 52 families in Dark Radar data, with 831,640 infection records.

Other names: Pure Logs Stealer, zgRAT

02

Origin and evolution

  1. 2022Went on sale as part of the PureCoder product family.Malpedia (Fraunhofer FKIE)
  2. 2025From version 5.0, traffic began to be wrapped mostly in TLS.Netresec
03

Technical profile

Malware typeInfostealer
Target operating systemWindows
Primary purposeData theft
Threat categoryCredential theft
Programming language.NET
Distribution modelSold by PureCoder
First seen2022
Infected systemsWindows 11 56%, Windows 10 34.5%
Public source confidenceMedium
04

Targeted applications

27 applications8 categories
05

Data collection

Credentials

  • Browser passwords100%Verified
  • Session cookies96.5%Verified
  • Refreshing expired sessions64%Dark Radar observation
  • Autofill93%Dark Radar observation
  • macOS Keychain—
  • 2FA and password managers—

Financial

  • Saved cardsVerified
  • Desktop crypto walletsVerified
  • Wallet extensionsVerified
  • Clipboard address replacement—

Applications

  • Email clients3.5%Dark Radar observation
  • FTP clients—
  • VPN clientsVerified
  • Messaging applicationsVerified
  • Gaming platforms4%Dark Radar observation

System

  • File collection—
  • Screenshot30%Dark Radar observation
  • System inventory7.5%Verified
06

File system

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

System components

  • System information
08

How it works

  1. 1Infection

    • Phishing emails; multi-stage .NET loaders (payloads hidden inside image files).

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

  2. 2Execution and evasion

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

  3. 3Discovery

    Dark Radar observation

    Infected systems: Windows 11 56%, Windows 10 34.5%.

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

  4. 4Data collection

    • Credentials and sensitive data are collected automatically.
    Dark Radar observation

    Data found in the latest 200 logs: password file 100%, cookies 96.5%, autofill 93%, cards 0.5%.

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

  5. 5Exfiltration and C2

    • Sending over a custom binary protocol on configurable ports.

    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

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?
  • Phishing emails; multi-stage .NET loaders (payloads hidden inside image files).
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?
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

Related terms

From the Essential plan

Infostealer Detection

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