Malicious Office (OLE) / .XLS — malware analysis report

Static analysis result for SHA-256 81ffd4964a93e3b7…

MALICIOUS

Office (OLE) / .XLS

1.11 MB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel First seen: 2023-09-20
MD5: 9032f044019161ceb48ad16bff220a09 SHA-1: c2aa0c449807c6af48a7d4dfc1ae768e32d90f4d SHA-256: 81ffd4964a93e3b7ba7a6308d8f8461b752ec2d038476b926a7a7ec0961ce818
272 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.001 Malicious Link: Malicious Link T1566 Phishing T1566.001 Phishing: Spearphishing Attachment T1059 Command and Scripting Interpreter

The sample is an Excel file containing an embedded Equation Editor object that exploits CVE-2017-11882. This object contains a secondary PDF payload which, in turn, has a direct link to an executable or archive. The VBA macros are empty, indicating the exploit is likely within the OLE object itself. The embedded PDF also exhibits parser evasion techniques.

Heuristics 8

  • Equation Editor Ole10Native payload — CVE-2017-11882 critical CVE likely CVE_2017_11882_EQUATION_OLE10NATIVE
    An embedded Microsoft Equation 3.0 object (CLSID 0002CE02-0000-0000-C000-000000000046) carries an Ole10Native packager stream instead of the normal Equation Native/MTEF data. This is the weaponized Equation Editor RCE delivery shape used by CVE-2017-11882 / CVE-2018-0802 maldocs. The payload (font-record overflow + shellcode) is frequently encrypted and the stream name case-scrambled to evade scanners, but an Equation object holding an Ole10Native stream has no benign use.
  • Equation Editor OLE object high CVE related OLE_EQUATION_EDITOR
    Contains Equation Editor object — related to CVE-2017-11882 / CVE-2018-0802 exploitation, but CLSID presence alone is not the malformed MTEF exploit primitive.
  • Secondary embedded PDF body has suspicious static findings critical POLYGLOT_CHILD_PDF_STATIC_TRIAGE
    A valid PDF body was found at a nonzero offset inside another container and its carved contents matched PDF exploit or lure heuristics. This catches polyglots where the top-level magic routes to ZIP/OLE while a PDF reader or downstream parser opens the hidden PDF payload.
  • PDF link points directly to executable/archive payload critical PDF_DIRECT_PAYLOAD_LINK
    PDF contains a clickable HTTP(S) URI whose path ends in an executable, script, shortcut, disk image, or archive extension. Documents can legitimately link to installers, so this is a high-risk delivery indicator rather than a standalone exploit fingerprint.
  • Clickable PDF combines external action with parser-evasion structure high PDF_ACTION_PARSER_EVASION
    PDF has an external clickable URI together with object graph or xref structures that make parsers disagree, such as divergent duplicate objects, parser divergence, or xref offset mismatch. That combination is stronger than a plain link: the document is both an outward-action carrier and a parser-confusion/evasion sample.
  • VBA project contains no executable statements low OLE_VBA_MACROS
    Document contains a VBA project, but extracted modules only contain attributes/options/comments and no executable statements.
  • Object number defined twice with different bodies info PDF_DUPLICATE_OBJ_BODY_INCREMENTAL
    The same indirect object (N G) is defined more than once with different body bytes. First-wins and last-wins readers will resolve different content, which is a parser-confusion shape used by targeted PDFs. Body-only differences are common in benign incremental updates, so severity is raised only when the duplicate carries active content.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL https://https://www.google.co.in/example.com
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/xap/1.0/
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://ns.adobe.com/pdf/1.3/

Extracted artifacts 7

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
7f506327609c082af1cd37dde23bc2c71a000f7d1ef530b6abb66775040a7673
vba-macro oletools.olevba.extract_macros (decoded VBA source) 1206 bytes
ole10native_00.bin
31142fb80e9bb8a3ac31c72b68e6170404a88b5a5f5c587f6f0accb09f327d0d
ole-package OLE Ole10Native stream: MBD000EB379/olE10NAtIVE 1876 bytes
polyglot_child_pdf_off0005ea00.pdf
2af90eb58247b7a1fab76ef3a7a512db9fc35ef0dbf09621b9f8359a0514d3d2
polyglot-child-pdf Secondary PDF body inside ole container at offset 0x5EA00 781312 bytes
stream_003_off00005f60.bin
2998a126f4fa11ceb265371a5f7968ec18bc4692a32631a544232dc74040021f
decompressed-pdf-stream PDF FlateDecoded stream at offset 0x5F60 252488 bytes
polyglot_child_pdf_off00001000.pdf
f6f9a04859a360f9e8329755aee9502f7564081575eb856735afbbadfb337d5c
polyglot-child-pdf Secondary PDF body inside ole container at offset 0x1000 1164800 bytes
polyglot_child_pdf_off00006600.pdf
e089ff947a4d7fdfadedf9cd554dee30179f43dfb7cbfaf524174cdc70c55f08
polyglot-child-pdf Secondary PDF body inside ole container at offset 0x6600 1142784 bytes
polyglot_child_pdf_off00029600.pdf
d2cffe4deb4464b5afcb99f1c6fbbd12e79e6e6ff82fb41f43f6ce71e7eedcfa
polyglot-child-pdf Secondary PDF body inside ole container at offset 0x29600 999424 bytes