# Análise de malware e ransomware

> Triagem de amostras, comportamento de ransomware, IOCs, YARA e Sigma.

Amostras PE, ELF, Mach-O, APK, macros, PDF e scripts, packers e unpacking, extração de configuração, classificação de famílias, estudo offline de protocolos de C2 e planejamento de recuperação de ransomware. Análise dinâmica se faz em laboratório isolado.

analyzing-android-dex-malware: Reverses Android malware: unpacking APKs, decompiling DEX bytecode to readable

analyzing-banking-trojan-webinjects: Analyzes banking trojan webinject configurations to extract targeted institutions,

analyzing-bootkit-and-rootkit-samples: Analyzes bootkit and advanced rootkit malware infecting the Master

analyzing-campaign-attribution-evidence: Systematically evaluate cyber-campaign evidence to attribute an operation to a threat actor, using the Diamond Model and Analysis of Competing Hypotheses (ACH) to weigh infrastructure overlaps, TTP consistency, malware code similarity, and timing/language artifacts into confidence-weighted attributi

analyzing-command-and-control-communication: Analyzes malware C2 communication over HTTP, HTTPS, DNS, and custom

analyzing-compiled-python-malware: Analyzes Python-based malware packaged as PyInstaller/py2exe executables by detecting

analyzing-cryptominer-malware: Analyzes cryptojacking/coinminer malware by extracting mining pool endpoints

analyzing-dotnet-malware-internals: Reverses .NET/managed malware: decompiling MSIL back to C#, defeating common

analyzing-excel-4-macro-malware: Analyzes legacy Excel 4.0 (XLM) macro malware by parsing extracted macro-sheet

analyzing-golang-malware-internals: Analyzes Go-compiled malware by recovering function names from the pclntab, detecting

analyzing-indicators-of-compromise: Analyzes indicators of compromise (IOCs) including IP addresses, domains,

analyzing-java-jar-malware: Analyzes Java/JAR malware (such as Adwind/jRAT-class cross-platform RATs) by

analyzing-macro-malware-in-office-documents: Analyzes malicious VBA macros embedded in Microsoft Office documents

analyzing-malware-behavior-with-cuckoo-sandbox: Detonate malware samples in Cuckoo Sandbox to observe runtime behavior

analyzing-malware-family-relationships-with-malpedia: Query the Malpedia API to look up malware family aliases and naming

analyzing-malware-in-memory-with-volatility3: Analyzes a memory image with Volatility 3 to find malware: rogue processes,

analyzing-malware-persistence-with-autoruns: Use Sysinternals Autoruns to systematically enumerate and analyze malware

analyzing-malware-sandbox-evasion-techniques: Detect sandbox and VM evasion techniques in malware samples by analyzing

analyzing-network-covert-channels-in-malware: Detect and analyze covert communication channels used by malware, including

analyzing-network-traffic-of-malware: Analyzes network traffic generated by malware during sandbox execution

analyzing-packed-malware-with-upx-unpacker: Identifies and unpacks UPX-packed malware samples, including binaries with modified UPX magic bytes or headers that block automated decompression, to recover the original executable for static analysis. Use when a sample shows high entropy, minimal imports, or only LoadLibrary/GetProcAddress in its

analyzing-pdf-malware-with-pdfid: Analyzes malicious PDF files using PDFiD, pdf-parser, and peepdf to

analyzing-ransomware-encryption-behavior: Analyzes how a ransomware sample encrypts files: identifying the crypto scheme

analyzing-ransomware-encryption-mechanisms: Analyzes encryption algorithms, key management, and file encryption

analyzing-ransomware-leak-site-intelligence: Safely monitor ransomware group Tor-hosted data leak sites (DLS) to collect and extract structured victim posting data, track group activity trends over time, and produce sector- and geography-specific ransomware risk assessments. Use when performing threat intelligence gathering on active ransomwar

analyzing-ransomware-network-indicators: Identify ransomware-related network indicators, including C2 beaconing patterns, TOR exit node connections, data exfiltration flows, and encryption key exchange, by analyzing Zeek conn.log and NetFlow data. Use when threat hunting for active ransomware network activity or investigating suspected pre

analyzing-ransomware-payment-wallets: Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs, identifying wallet clusters and tracking fund movement through mixers and exchanges to support law enforcement attribution. Use when tracing ransomware

analyzing-rat-command-and-control: Analyzes remote access trojan command-and-control by mapping the RAT command set,

analyzing-rust-malware-internals: Analyzes Rust-compiled malware by detecting the Rust toolchain signature, demangling

analyzing-supply-chain-malware-artifacts: Investigate supply chain attack artifacts including trojanized software

analyzing-threat-landscape-with-misp: Query a MISP (Malware Information Sharing Platform) instance via PyMISP

analyzing-wiper-malware: Analyzes destructive wiper malware by identifying raw-disk and MBR/VBR overwrite

automating-ioc-enrichment: Automates the enrichment of raw indicators of compromise with multi-source

building-a-sample-management-workflow: Establishes a disciplined malware sample repository: content-addressed storage by

building-automated-malware-submission-pipeline: Builds an automated malware submission and analysis pipeline that collects

building-config-extractors: Builds reusable malware configuration extractors by applying a declarative JSON spec

building-detection-rules-with-sigma: Builds vendor-agnostic detection rules using the Sigma rule format for

building-ioc-defanging-and-sharing-pipeline: Build an automated pipeline that ingests raw IOCs (URLs, IPs, domains,

building-ioc-enrichment-pipeline-with-opencti: Build an automated IOC enrichment pipeline on OpenCTI (STIX 2.1 native

building-malware-incident-communication-template: Build structured communication templates for malware incidents (ransomware,

building-ransomware-playbook-with-cisa-framework: Builds a structured ransomware incident response playbook aligned with

bypassing-anti-vm-and-sandbox-checks: Bypasses anti-VM and sandbox checks during analysis by locating the specific detection

capturing-and-analyzing-malware-network-traffic: Captures and analyzes malware network traffic from a detonation: extracting C2

collecting-threat-intelligence-with-misp: Deploy MISP, configure threat feeds (MISP community, freetext, TAXII, CSV), and use the PyMISP API to programmatically fetch, add, and search events and IOCs, building automated collection pipelines that aggregate indicators from community and commercial sources. Use when gathering, storing, or corr

competition-bundle-sourcemap-recovery: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for source maps, build manifests, chunk registries, emitted bundles, obfuscated loader flow, and frontend runtime recovery. Use when the user asks to reconstruct served JavaScript structure, inspect source maps or chunk map

competition-custom-protocol-replay: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for custom binary or text protocol recovery, handshake reconstruction, framing, sequence control, checksums, stateful replay, and accepted-session reproduction. Use when the user asks to decode an unknown protocol, recover

competition-dpapi-credential-chain: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for DPAPI masterkeys, vault blobs, browser credential stores, protected secrets, domain backup keys, and secret-to-acceptance replay chains. Use when the user asks to inspect DPAPI blobs or masterkeys, recover browser or va

competition-file-parser-chain: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for file uploads, imports, previews, archive extraction, format conversion, parser invocation, and deserialization chains. Use when the user asks to inspect an upload or import path, trace archive extraction, preview or con

competition-lsass-ticket-material: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for LSASS-resident secrets, Windows logon sessions, Kerberos ticket caches, DPAPI-backed material, SSP artifacts, and replayable credential extraction. Use when the user asks to inspect LSASS memory, recover tickets or logo

competition-mailbox-abuse: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for enterprise mail abuse, OAuth consent, inbox or forwarding rules, transport rules, shared mailbox access, phishing chains, and token-to-mailbox side effects. Use when the user asks to trace mailbox rules, OAuth consent g

competition-malware-config: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for malware configuration recovery, staged payload boundaries, beacon parameter extraction, and IOC decoding. Use when the user asks to recover a malware config, decode C2 or beacon fields, unpack staged payloads, extract b

competition-queue-worker-drift: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-

competition-race-condition-state-drift: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for race windows, ordering bugs, idempotency failures, lock gaps, concurrent worker drift, and state inconsistencies that produce decisive effects. Use when the user asks to reproduce timing-sensitive bugs, concurrent state

competition-relay-coercion-chain: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for forced-auth coercion, relay chains, target selection, NTLM or related acceptance paths, and coercion-to-privilege transitions. Use when the user asks to trace a coercion primitive, follow a relay path, analyze forced au

competition-request-normalization-smuggling: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for parser differentials, HTTP normalization gaps, ambiguous headers, path decoding drift, transfer-framing mismatches, and request smuggling routes. Use when the user asks to trace proxy and backend parse differences, conf

competition-runtime-routing: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse proxies, Host headers, forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting, base-URL derivation, and multi-node route resolution. Use when the user asks which host or container serves a r

competition-stego-media: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for image, audio, video, document, and container steganography. Use when the user asks to inspect metadata, alpha or palette channels, LSBs, thumbnails, appended trailers, QR fragments, transcoding artifacts, or recover a h

competition-supply-chain: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CI/CD, registry, dependency drift, artifact provenance, image build, release pipeline, and runtime consumer challenges. Use when the user asks to trace dependency drift, registry pulls, malicious packages, build or rele

competition-template-render-path: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps. Use when the user asks to inspect SSR or template routes, trace render context or hy

competition-websocket-runtime: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for WebSocket and SSE handshakes, auth material, subscription state, realtime message schemas, reconnect behavior, and frame-driven runtime effects. Use when the user asks to inspect a WebSocket or SSE handshake, decode fra

competition-zip-archive: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for ZIP and PKZIP archive challenges, legacy ZipCrypto identification, known-plaintext recovery with bkcrack, key-based decryption, and reproducible extraction. Use when the user asks to solve an encrypted ZIP challenge, in

conducting-malware-incident-response: Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware inf

correlating-threat-campaigns: Correlates disparate security incidents, IOCs, and adversary behaviors

ctf-sandbox: Thin PRIMARY for CTF / AWD / 靶场 multi-type orchestration. Hands off to the sidecar CTF-Sandbox-Orchestrator. Use when the user says CTF, AWD, 靶场, or 比赛题 and no more specific pwn/APK/IDA route already won.

ctf-sandbox-orchestrator: Default entrypoint and master ctf-sandbox-orchestrator workflow for CTF, exploit, reverse engineering, DFIR, pwnable, crypto, stego, mobile, AI-agent, cloud, container, Active Directory, Windows-host, and identity challenges. Use first when the user presents challenge infrastructure, binaries, promp

defanging-and-sharing-iocs: Prepares indicators of compromise for safe sharing: defanging URLs, domains, IPs,

defense-detection-sigma: Write portable detections as Sigma rules and map them to MITRE ATT&CK, then convert to your SIEM. Load for blue-team/detection-engineering tasks: "write a detection", "sigma rule", "alert on", turning an offensive technique or an incident into a repeatable detection.

defense-malware-triage: Safely triage a suspicious file or process — is it malicious, what does it do, and what IOCs does it yield — with static then dynamic analysis. Load for "is this file malware", "analyze this binary/script/document", "suspicious process on a host", or extracting IOCs for hunting/detection.

defense-threat-intel: Enrich IOCs, campaigns, impersonation, and scam narratives from public sources — bounded public X/Twitter collection via Xquik plus independent corroboration — and hand off a reviewable intelligence package. Load for "enrich this IOC", "is this domain in recent phishing disclosures", tracking threat

deobfuscating-javascript-malware: Deobfuscates malicious JavaScript found in phishing pages, web skimmers, and dropper scripts by reversing encoding layers, eval chains, string manipulation, and control-flow obfuscation to reveal the original malicious logic. Use when investigating a phishing page's obfuscated JavaScript, analyzing

deobfuscating-powershell-obfuscated-malware: Systematically deobfuscates multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure. Use during incident response or malware analysis when a PowerShell script is obfuscated with encoding, string manip

deploying-decoy-files-for-ransomware-detection: Deploys canary files (honeytokens) across file systems to detect ransomware

deploying-ransomware-canary-files: Deploys and monitors ransomware canary files using Python's watchdog library, placing decoy files mimicking high-value targets (financial records, credentials, database exports) where ransomware enumerates first, and alerting via email, Slack, or syslog on any read/modify/rename/delete. Use for earl

detecting-fileless-attacks-on-endpoints: Detects fileless malware and in-memory attacks that execute entirely

detecting-fileless-malware-techniques: Detects and analyzes fileless malware that operates entirely in memory

detecting-malicious-npm-packages: Triage npm packages and lockfiles for install-script malware, credential exfiltration, and worming behavior using GuardDog, manual tarball inspection, and dynamic detonation with network/filesystem monitoring. Use when vetting a new dependency, reviewing a package.json/package-lock.json during code

detecting-process-injection-techniques: Detects and analyzes process injection techniques used by malware including

detecting-ransomware-encryption-behavior: Detects ransomware encryption activity in real time using entropy

detecting-ransomware-precursors-in-network: Detects early-stage ransomware indicators in network traffic before

detecting-sandbox-evasion-behavior: Detects sandbox and analysis evasion techniques in a sample by scanning static

diffing-malware-samples-to-find-changes: Compares two related malware samples to surface what changed between variants using

enriching-iocs-with-threat-intel-sources: Enriches indicators with context from threat-intel sources: planning lookups against

eradicating-malware-from-infected-systems: Systematically map and remove malware, backdoors, and attacker persistence

extracting-config-from-a-running-sample: Extracts an embedded malware configuration (C2 hosts, ports, campaign IDs, keys) from

extracting-iocs-from-analysis-output: Extracts indicators of compromise from raw analysis artifacts: parsing strings

extracting-iocs-from-malware-samples: Extracts indicators of compromise (IOCs) from malware samples, including

handling-malware-samples-safely: Establishes safe practices for acquiring, storing, transferring, and disposing

hashing-and-fingerprinting-files: Computes cryptographic and fuzzy fingerprints for malware samples: MD5/SHA-1/SHA-256

hunting-ransomware-precursor-behavior: Hunts for ransomware precursor behavior that precedes encryption — shadow-copy and

identifying-file-types-and-formats: Identifies a sample''s true file type independent of its extension: matching magic

implementing-anti-ransomware-group-policy: Configures Windows Group Policy Objects to block ransomware execution

implementing-honeypot-for-ransomware-detection: Deploys canary files, honeypot shares, and decoy systems to detect ransomware

implementing-immutable-backup-with-restic: Implements ransomware-resistant backups using restic with S3-compatible

implementing-mimecast-targeted-attack-protection: Deploys and configures Mimecast Targeted Threat Protection (TTP) modules -- URL Protect (click-time URL rewriting/analysis), Attachment Protect (sandbox detonation), Impersonation Protect (BEC/whaling detection), and Internal Email Protect -- for Microsoft 365 or Google Workspace. Use when defending

implementing-ransomware-backup-strategy: Designs a ransomware-resilient backup strategy using the 3-2-1-1-0

implementing-ransomware-kill-switch-detection: Analyzes ransomware kill switch mechanisms, including mutex-based execution

investigating-ransomware-attack-artifacts: Forensically preserve memory and disk, collect ransom notes and encrypted file samples, and identify the ransomware variant using tools such as ID Ransomware, Volatility, and Chainsaw/Hayabusa to determine the initial access vector and recovery options. Use immediately after discovering ransomware e

malware-analysis: Use when analyzing suspected malware through static, dynamic, and behavioral techniques, including IOC extraction, YARA or Sigma rules, sandboxing, and anti-analysis behavior.

malware-triage: Safely triage unknown malware samples — static indicators, sandbox execution, behavior extraction, and reporting. Use when analyzing suspicious files during investigations.

modeling-threats-with-opencti: Deploy OpenCTI (Filigran) via Docker Compose and use the pycti Python client to model threat actors, intrusion sets, campaigns, and indicators as a STIX 2.1 knowledge graph with relationships (uses, attributed-to, targets). Use when building a centralized threat-intel knowledge base, correlating IOC

monitoring-darkweb-sources: Monitors dark web forums, marketplaces, paste sites, and ransomware

monitoring-process-and-file-behavior: Summarizes runtime behavior of a sample from Procmon-style operation logs — process

offensive-cicd-pipeline: Comprehensive CI/CD pipeline exploitation methodology covering GitHub Actions injection vectors (expression injection via PR titles and issue bodies, workflow_run event abuse, GITHUB_TOKEN over-scoping, composite action supply chain compromise), Jenkins attack paths (Groovy sandbox escapes, script c

operationalizing-misp-threat-feeds: Stand up MISP, enable and cache curated threat feeds (CIRCL, abuse.ch, Feodo Tracker), apply warninglists to suppress false positives, query indicators with PyMISP, and export attributes as auto-generated Suricata/Sigma/Wazuh detection rules. Use when maturing a MISP instance to actively drive detec

performing-automated-malware-analysis-with-cape: Deploy and operate the CAPEv2 malware sandbox (a Cuckoo derivative) to run samples in a

performing-dynamic-analysis-in-a-sandbox: Runs a sample in an instrumented sandbox to observe behavior: process tree, file

performing-dynamic-analysis-with-any-run: Perform interactive dynamic malware analysis using the ANY.RUN cloud sandbox

performing-indicator-lifecycle-management: Tracks IOCs through discovery, enrichment/validation (VirusTotal, Shodan,

performing-ioc-enrichment-automation: Automates Indicator of Compromise (IOC) enrichment by orchestrating

performing-malware-hash-enrichment-with-virustotal: Enrich malware file hashes (MD5, SHA-1, SHA-256) using the VirusTotal

performing-malware-ioc-extraction: Malware IOC extraction is the process of analyzing malicious software

performing-malware-persistence-investigation: Systematically investigate all persistence mechanisms on Windows and

performing-malware-triage-with-yara: Performs rapid malware triage and classification using YARA rules that

performing-ransomware-response: Executes a structured ransomware incident response from detection through

performing-ransomware-tabletop-exercise: Plans and facilitates tabletop exercises simulating ransomware incidents,

performing-threat-hunting-with-yara-rules: Use YARA pattern-matching rules to hunt for malware, suspicious files,

performing-threat-intelligence-sharing-with-misp: Uses PyMISP (the official MISP REST API library) to create events with structured IOCs (IPs, domains, hashes, URLs), enrich them with MITRE ATT&CK tags and galaxy clusters, manage sharing groups and distribution levels, search existing intelligence, and export in STIX 2.1 format. Use when creating,

performing-yara-rule-development-for-detection: Develops precise YARA and YARA-X rules for malware detection by identifying

recovering-from-ransomware-attack: Executes structured ransomware incident recovery following NIST/CISA

reverse-engineering-ransomware-encryption-routine: Reverse engineer ransomware encryption routines to identify cryptographic

reverse-eng-malware: Fully analyze a malware sample — static, dynamic, and behavioral — including unpacking and IAT rebuild, import-table triage, anti-analysis detection and defeat, IOC extraction, and YARA/Sigma rule writing. Load when handed a suspicious PE/ELF/Mach-O/script sample to reverse beyond quick triage: pack

scanning-samples-with-yara: Uses YARA to classify and triage samples at scale: applying rule sets, reading

setting-up-an-isolated-malware-analysis-lab: Builds a safe, isolated environment for detonating and analyzing malware

shellcode-analyzer: Load, unpack, and analyze shellcode in x64dbg. Use this skill when the user wants to analyze shellcode, load a shellcode blob into a debugger, unpack encoded/encrypted shellcode, or perform static/dynamic analysis of shellcode payloads.

testing-ransomware-recovery-procedures: Tests and validates ransomware recovery procedures - backup restore operations

threat-intelligence: Use for authorized OSINT and cyber threat intelligence that enriches IOCs, campaigns, impersonation, scams, or threat actors from public sources. Includes bounded X/Twitter search through Xquik, source preservation, corroboration, and evidence handoff.

triaging-an-unknown-sample: Performs fast first-pass triage of an unknown file to decide depth of analysis:

unpacking-upx-and-common-packers: Identifies and unpacks packed binaries: detecting packers from section names and

writing-a-malware-analysis-report: Structures a clear, actionable malware analysis report covering summary,

writing-sigma-detection-rules: Converts hunt findings into portable Sigma detection rules: choosing the right

writing-suricata-and-snort-rules: Writes and validates Suricata/Snort IDS rules for network-based malware detection,

writing-yara-rules-from-reversed-code: Turns reverse-engineering findings into durable YARA detections: selecting stable

yara: Auth/lab ref: YARA pattern matching; files, binaries, memory images, strings/regex/byte rules, malware/stego/IOC classification.

yara-rule-authoring: Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malwa

yara-sigs: Scan a state snapshot's memory dumps with YARA signatures to detect packers, crypto constants, malware, and more

Canonical: https://notholy.com/pt-br/skills/category/malware-analysis
