2026-10-24 14:40 UTC
----------------
🛠️ Tool: PacketSmith v5 Integrates Yara-X into Network Traffic Analysis
===================
PacketSmith from Netomize shipped version 5, codenamed Pinus strobus, and the headline feature is an integrated Yara-X engine. The vendor describes the release as the result of extended R&D for network detection engineers, SOC analysts, and malware and vulnerability researchers, adding "unique, unparalleled" capabilities. Marketing aside, the integration itself looks substantive: Yara-X is not only pointed at payloads, it is wired into a structure of protocol attributes that the compiler can reference.
Key features
• Scoping across data categories: raw frames, individual TCP/UDP packets, reassembled TCP/UDP streams, and ICMP (v4/v6) payloads.
• Deep protocol attributes provided as custom Pattern Identifiers (PaIDs), nested identifiers that let rules target network metadata instead of raw bytes only.
• Cross-layer correlation: a single YARA condition can reference link-layer, network-layer, and transport-layer dissected data simultaneously.
• Results as high-detail console output, JSON, or XML Workbook, with the option of logging matched content.
Technical implementation
The dns case study is the most concrete part of the announcement. It targets the Denis backdoor, publicly documented by Kaspersky on Securelist under "Use of DNS tunneling for C&C communications".
Sample indicators:
MD5: 1a4d58e281103fea2a4ccbfab93f74d2
SHA-1: 1a2cd9b94a70440a962d9ad78e5e46d7d22070d0
SHA-256: f5872f49943c39b73026fc3982b85330953a138cc27c23487a28103337bfdbb5
Win32 EXE, Microsoft Visual C++, 179,202 bytes
Detected behavior: the malware sends check-in DNS requests to Google's public resolver 8.8.8.8 on port 53, base64-encoded with the custom alphabet [A-Za-z0-9_-], and the initial check-in consists of one tunneling label at a fixed 32-byte length. The vendor ships a reference capture (denis_bkdr_dns, 2,292 bytes) together with a sample rule combining ip4 and dns PaIDs. The rule condition shown:
dns.is_set and not dns.over_tcp and not dns.flag.response
and dns.flag.opcode == 0
// optional check:
ip4.is_set and ip.dst.addr == "8.8.8.8"
Use cases
1. Detection engineering against known malware captures, where rules are validated directly on pcaps.
2. Tunneling signatures built on protocol structure, which holds when payload content is encrypted, since the pattern lives in field shape, resolver choice, and flag combinations.
3. Offline pcap triage. The vendor's own analogy: PacketSmith plus Yara-X is to a pcap what an IDS/IPS is to live traffic.
Limitations and open questions
• The claim that no other tool on the market has this capability is vendor-provided and unverified.
• The post demonstrates only the ip4 and dns PaIDs. The announced protocol list at other layers is larger, but per-protocol identifiers require the official documentation.
• The sample rule is tailored to this sample's fixed 32-byte label, so expect tuning for other tunneling families and false-positive pressure from legitimate long DNS labels.
• The release material is framed around pcap analysis; nothing in the post describes high-volume live traffic handling.
References
• PacketSmith official documentation, with technical specifications and advanced use cases for identifying malware C&C traffic and network exploitation attempts.
• Kaspersky Securelist: Use of DNS tunneling for C&C communications.
🔹 tool #PacketSmith #YaraX #NetworkDetection #DNSTunneling
🔗 Source: https://packetsmith.ca/yara-x-packetsmith-detection-module/
Replies (0)
No replies.