unpack#6

Malware unpacking · 2 objects · 1 static report · generated 2026-10-16 17:07:40 UTC

Task outcome

0 unpacked objects

Analysis summary

No payload was recovered from the x64 Go executable: scans found no validated embedded file or extracted stage, only certificate data. High-entropy `.rdata` and Base64-, RC4-, and AES-like code matches are inconclusive; no decoding chain, payload boundary, or keys were established, leaving a possible concealed stage unresolved.

Read full analysis
  • No unpacked samples were returned.

Kesakode detections

No Kesakode detections recorded.

Inspect the evidence

Selected static findings, linked to their source objects. Matches are not necessarily malicious. A lack of matches does not establish that the file is safe.

Unpacked objects

No unpacked object was returned.

Unpacking report

File description

The submitted file (unpack#6) is an 8,924,536-byte PE for x64. Its SHA-256 is 33df5d6b61564f89fb40a5c32fc059b1d15fd7971bf3c6db9671100c3ff673f8. Malcat identifies Go, and the embedded build information reports Go 1.21.9. The entry point is 0x004657a0 (EntryPoint).

Strings in include a CLI-like sequence of add, find, snapshot, diff, and report commands. This describes visible program content, not a separately recovered payload.

Container handling

has no listed virtual files and is not identified as an archive or installer. The carved-file scan found only a PKCS#7 certificate at #880e08 (<Certificate>+8) in the overlay; this is certificate data, not a payload. No #UPX.Unpacked virtual file or other extracted stage was available.

No specific supported loader or malware family was identified that would warrant a custom unpacker. The certificate metadata names “Aurora Craft”; that metadata does not establish a payload or a trusted signature.

Packing evidence

Malcat reports a large .rdata section in with entropy 194/255, plus 147 high-entropy-buffer anomaly hits, cross-section jumps, and section-size anomalies. Representative intervals are highly entropic: 64 KiB at 0x00860000 (.rdata:212000) measured 227/255, and 16 KiB at 0x00845951 (.rdata:1f7951) measured 230/255. These observations are suspicious enough to note, but do not by themselves identify packed or encrypted payload bytes.

The scan found no virtual or carved payload beyond the certificate. A one-shot scan found no validated embedded PE and no ZIP, gzip, 7z, RAR, CAB, or ELF header match. Repeated MZ byte matches did not validate as embedded PE files. Malcat’s YARA results identify Go and process-enumeration patterns, but no packer signature. Given the Go build metadata and lack of a demonstrated payload boundary or loader, the high-entropy data remains inconclusive rather than a confirmed concealed stage.

Encryption/packing methods and keys found

Capa reports Base64-like code, RC4-like loops, and AES instructions in . These are code-pattern matches; the analysis did not establish that they decrypt or decode the high-entropy intervals. No linked payload-decoding chain, key, IV, or transform parameters were recovered. Applying transforms to the opaque intervals would therefore be speculative.

Result and limitation: No payload was recovered. The strongest unresolved lead is the high-entropy .rdata data, for which static analysis did not establish a payload format, extraction boundary, or matching decryptor.