Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/capturing-and-analyzing-malware-network-trafficMalware and ransomware analysis

capturing-and-analyzing-malware-network-traffic

⁨Captures and analyzes malware network traffic from a detonation: extracting C2⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/capturing-and-analyzing-malware-network-traffic

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
w0gn6k4+uR…l3wZTfAQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package77ffcab2…1011971c
77ffcab250be…77ac1011971c4 files · ⁦3.9 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/capturing-and-analyzing-malware-network-traffic@da7600a

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:

bash
python scripts/analyst.py summarize capture.pcap

Step 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.md for the PCAP summarizer and beaconing detector.
  • Wireshark and Zeek documentation (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesYesYes
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a77ffcab2Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login