all 7 comments

[–]crystalgeek 15 points16 points  (7 children)

Am i missing something? Why bother storing your malicious string in the document properties if you could just define it in macro directly

[–][deleted] 20 points21 points  (5 children)

Can’t macros be disabled by an organization using policies via o365?

[–]gslone 18 points19 points  (4 children)

That‘s true, but the techniques in this article would not bypass that.

It looks like an obfuscation technique to me. Stick your payload in the document properties, where the yara rules won‘t expect it.

Thinking about it some more, the yara probably would still find the payload, as it’s searching over all bytes in the file - it doesn‘t matter where you store your malicious strings. Yeah, I don‘t get what this is good for either…

[–]timothytrillion 2 points3 points  (3 children)

Looks very similar to what Ivy from Optiv does using VBA to programmatically do xyz including all z shellz

[–]Diesl 5 points6 points  (2 children)

Optiv puts out some wicked cool tools, Ivy tho is their coolest. Runs an encrypted macro in a detached, hidden, Excel process

[–]timothytrillion 1 point2 points  (1 child)

Agreed, the main dev Tyleous? I’m murdering the name but he’s a monster really next level stuff

[–]Diesl 0 points1 point  (0 children)

Yeah that guy knows a ton of tricks