capturing-and-analyzing-malware-network-traffic
Captures and analyzes malware network traffic from a detonation: extracting C2
v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/capturing-and-analyzing-malware-network-trafficScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto77ffcab2…1011971c
77ffcab250be…77ac1011971c4 file · 3.9 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/capturing-and-analyzing-malware-network-traffic@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- You detonated a sample and captured a PCAP on the services guest, and need to extract its network behavior.
- You want C2 endpoints, HTTP/DNS patterns, TLS SNI/JA3, and beaconing intervals.
- You are turning traffic observations into network IOCs and detection signatures.
Do not use a single capture as the full C2 picture — staged samples reveal more on longer runs or with the right context. Combine with binary config extraction.
Prerequisites
- A PCAP captured from the isolated lab (capture on the analysis guest, not the victim).
tshark/Wireshark, or Zeek for connection logs, or the bundled PCAP summarizer.- The lab's simulated-internet IP so you can separate sample traffic from noise.
Safety & Handling
- Capture from the services/analysis guest so the victim never hosts a sniffer.
- Defang all extracted domains/IPs/URLs before sharing.
Workflow
Step 1: Get a connection overview
Summarize conversations and protocols to see who talks to whom and how often:
python scripts/analyst.py summarize capture.pcapStep 2: Analyze DNS
List queried domains and resolved IPs. Look for DGA-like randomness, repeated NXDOMAIN, and long TXT records (possible tunneling).
Step 3: Inspect HTTP/HTTPS
For HTTP, examine URIs, methods, User-Agent (often unique/odd), and POST bodies. For HTTPS, extract SNI and JA3/JA3S fingerprints since payloads are encrypted.
Step 4: Detect beaconing
Compute inter-arrival times to the same destination. Regular intervals (with jitter) to one host indicate C2 check-ins.
Step 5: Build IOCs and detection
Produce a network IOC set (domains, IPs, URIs, JA3, User-Agent) and hand candidate signatures to the Suricata/Zeek detection workflow.
Validation
- Beaconing intervals are consistent and tied to a specific destination, not random browsing.
- Extracted SNI/JA3 reproduce across runs of the same sample.
- DNS and HTTP observations corroborate the C2 endpoints found in the binary's config.
Pitfalls
- Mistaking simulated-internet responses for real C2 behavior; know your lab's IPs.
- Ignoring HTTPS because it is encrypted — SNI, JA3, and timing are still strong signals.
- Treating one short capture as complete; some C2 only beacons periodically.
References
- See
references/api-reference.mdfor the PCAP summarizer and beaconing detector. - Wireshark and Zeek documentation (linked in frontmatter).
File di questa versione
references/11.3 KB
- api-reference.md1.3 KB
scripts/14.3 KB
- analyst.py4.3 KB
- LICENSE340 B
- SKILL.md3.3 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | Sì | Sì |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 77ffcab2 | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
Altro in Analisi di malware e ransomware
Vai alla categoria- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login