Fraudpack

Overview

TrojanDropper:Win32/Fraudpack is a persistent, stealthy trojan designed specifically to breach endpoint defenses and securely drop secondary, high-severity payloads (almost exclusively Rogue Security Software and Scareware) directly onto the file system.

Understanding Fraudpack
To an end-user, a Fraudpack infection is typically invisible until the devastating secondary payload executes—which, in this case, results in the screen being flooded with fake antivirus alerts. For threat intelligence analysts, Fraudpack is a critical staging mechanism. Unlike a standard downloader that fetches code from the internet, a 'Dropper' actually contains the secondary payload embedded within its own code structure. Its primary objective is to securely bypass endpoint defenses, extract the embedded scareware payload, and execute it.

Execution and Evasion Strategies
Fraudpack is commonly distributed via massive malvertising campaigns, drive-by downloads, or exploit kits. Upon execution, it utilizes heavy packing and obfuscation to evade static antivirus signatures (`T1027`). Once running, it unpacks its internal payload (the actual rogue antivirus software) and writes it (drops it) to a strategic location on the disk, such as `%Temp%` or `%AppData%`. It then executes this dropped file. Fraudpack often uses techniques like 'timestomping' (`T1070.006`) to make the dropped file appear legitimate and establishes persistence for the scareware payload via Registry Run keys.

Indicators of Compromise (IoCs)
Threat hunters should investigate EDR alerts related to suspicious file creation events in user profile directories followed immediately by the execution of that newly created file, which then begins creating massive amounts of UI manipulation and fake alerts. Because the payload is embedded, network IoCs for the initial stage may be minimal. Memory analysis and static reverse engineering of the Fraudpack binary are necessary to extract the embedded payload.

MITRE ATT&CK Techniques

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

Tactical Mitigations

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

• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.

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_FRAUDPACK {
    meta:
        description = "Detects Fraudpack (trojan)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "fraudpack" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

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

Containment & Response Steps

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

1. Isolate the endpoint immediately to prevent the secondary scareware payloads dropped by Fraudpack from exfiltrating data or locking the system.
2. Audit the Windows Task Scheduler and Registry Run keys to identify and remove the persistence mechanisms established for the dropped payload.
3. Perform a deep forensic scan of the `%AppData%` and `%Temp%` directories to locate and remove all executables dropped by the initial infection vector.
4. Submit the original Fraudpack executable to a sandbox to extract and analyze the embedded secondary payload.

What to Avoid

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

1. Do not close an incident simply because the initial Fraudpack executable was quarantined; the embedded scareware payload was likely already dropped and running.
2. Avoid relying solely on static hash sweeping; Droppers frequently re-pack their binaries to generate novel hashes for every campaign.

References & External Analysis

• Search "fraudpack" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: trojan)

Explore other malware families in the same category:

• Otorunq
• Sohanad
• Bnksa
• Hafen
• Krbanker

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/fraudpack.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.