Query the Malpedia API to look up malware family aliases and naming (platform.family_name), pull community/vendor YARA rules, link families to threat actors, and map family relationships such as loader-payload chains and shared authorship. Use when researching a malware family's aliases, lineage, or

Analyzing Malware Family Relationships with Malpedia Overview Malpedia is a collaborative platform maintained by Fraunhofer FKIE that catalogs malware families with their aliases, YARA rules, threat actor associations, and reference reports. With over 2,600 malware families documented, it serves as the definitive resource for understanding malware lineages, tracking variant evolution, and linking malware to specific threat groups. This skill covers querying the Malpedia API, mapping malware family relationships, extracting YARA rules for detection, and building intelligence on malware ecosystems used by adversaries. When to Use When investigating security incidents that require analyzing malware family relationships with malpedia When building detection rules or threat hunting queries for this domain When SOC analysts need structured procedures for this analysis type When validating security monitoring coverage for related attack techniques Prerequisites Python 3.9+ with requests , yara python , stix2 libraries Malpedia API key (register at https://malpedia.caad.fkie.fraunhofer.de/) Understanding of malware classification and naming conventions Familiarity with YARA rule syntax for detection Access to malware samples for validation (optional) Key Concepts Malpedia Data Model Malpedia organizes malware into Families (e.g., "win.cobalt strike"), each containing: aliases (vendor specific names like "Beacon", "CobaltStrike"), YARA rules (community and vendor contributed), actor associations (threat groups using the family), reference reports (CTI reports documenting the family), and sample hashes (representative samples for each variant). Malware Family Naming Malpedia uses the format platform.family name (e.g., win.emotet , elf.mirai , apk.flubot ). Platforms include win (Windows), elf (Linux), apk (Android), osx (macOS), and py (Python). This standardized naming resolves the "many names" problem where different vendors assign different names to the same malware. Family Relationships Malware families have relationships including: parent child (code reuse, forks), loader payload (Emotet loads TrickBot loads Ryuk), shared authorship (same threat actor develops multiple tools), and infrastructure sharing (common C2 frameworks). Workflow Step 1: Query Malpedia API for Malware Families Step 2: Map Malware Family Relationships Step 3: Extract and Compile YARA Rules Validation Criteria Malpedia API queried successfully for malware families Family information retrieved with aliases, actors, and references Actor family relationships mapped correctly Shared tooling between actors identified YARA rules extracted and compiled for detection Loader payload chains documented for threat intelligence References [Malpedia Platform](https://malpedia.caad.fkie.fraunhofer.de/) [Malpedia API Documentation](https://malpedia.caad.fkie.fraunhofer.de/usage/api) [Malpedia Research Paper](https://www.botconf.eu/wp content/uploads/formidable/2/2017 DanielPlohmann Malpedia.pdf) [YARA Rules Project](https://github.com/Yara Rules/rules) [malwoverview Multi Platform Tool](https://github.com/alexandreborges/malwoverview) [CyberAtlas: Malpedia Integration](https://www.cyberatlas.io/malpedia)

analyzing-malware-family-relationships-with-malpedia