Win.Trojan.Surabaya-3 Office (OLE) malware analysis — malicious · 0339df2824b28c34

MALICIOUS

Office (OLE)

21.5 KB Created: 1993-09-28 16:08:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14

MD5: ab20ae35af1e9988c91dff747bcc9f2c SHA-1: 1d9bc37073bafa7168143678cdb3a78438b9dca4 SHA-256: 0339df2824b28c341899aa0632b2dddf6af808d36a1766880163522cf3f2ea65

180 Risk Score

Malware Insights

Win.Trojan.Surabaya-3 · confidence 95%

MITRE ATT&CK

T1059.005 Visual Basic

The file contains legacy WordBasic macro virus markers and is detected by ClamAV as Win.Trojan.Surabaya-3. The embedded OLE object also exhibits suspicious static findings, including empty streams and a FAT chain loop, indicating potential obfuscation or corruption. The macro's authoring information suggests it is designed to execute malicious code.

Heuristics 4

ClamAV: Win.Trojan.Surabaya-3 critical CLAMAV_DETECTION

ClamAV detected this file as malware: Win.Trojan.Surabaya-3
Embedded Office document has suspicious static findings critical EMBEDDED_OFFICE_CHILD_STATIC_TRIAGE

A CFB/OLE Office document was found inside another file type and its carved contents matched Office exploit or payload heuristics. This catches wrapped exploit documents where the top-level file routes to a PE, archive, or generic scanner instead of Office.
Legacy WordBasic macro-virus markers high OLE_LEGACY_WORDBASIC_MACRO_VIRUS

OLE Word document contains legacy WordBasic auto-execution macro markers such as AutoOpen plus ToolsMacro/MacroFile/fileMacro/globMacro or named historical macro-virus strings. These old Word 6/95 macro forms are not exposed as a modern VBA project, so normal VBA source extraction can miss them.
CFB header with no readable streams medium OLE_PARSE_EMPTY_STREAMS

This finding applies to a carved embedded Office document found at a nonzero offset inside the submitted file, not directly to the top-level document. The file begins with a valid OLE2/CFB header but exposes no directory streams. A non-empty compound document with an unreadable directory is anomalous — it is seen with truncated/corrupt files and, more importantly, with content deliberately shifted off byte boundaries to defeat parsers while the host application still recovers the object.

Extracted artifacts 1

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`embedded_office_off00002100.ole`	embedded-office	Embedded OLE/CFB Office body inside ole container at offset 0x2100	13568 bytes
SHA-256: `1fdd29c3e15a06238d1141c1d76f534aa5ab7c25ea3f6eca0e314d290df004c7`

Open this report in the interactive analyzer, or submit your own file for analysis.