\objupdate activation with payload hidden outside \objdata

The document combines \objupdate (which forces Word to instantiate the embedded OLE object on open, with no user interaction) and a bare \object declaration that carries NO \objdata destination. The object's payload is instead dumped as a multi-hundred-kilobyte hex-encoded region in the raw document body. This split placement hides the payload from parsers that only decode \objdata blobs, while Word still activates the object. The shape is structurally exclusive to weaponised documents; across the corpus this combination is ~99% malicious, and the detector specifically covers the variant whose payload is opaque/encrypted and therefore leaves no decodable OLE, Equation Editor, or PE fingerprint for the signature-attributed rules.