Re:Investigating a malware sample which sometimes fails to b...
by 13of40 on Sunday September 25, 2016 @02:49AM
(#12574289)
The funny thing about these is that the obfuscator leaves a billion clues that can tip you off that the macro is malicious, without even having to run it. Any human being can tell you that DKTxHE is a bogus name for a function, so the only trick is to implement that detection in code...
[ Parent
| on HN ]
Re:Investigating a malware sample which sometimes fails to b...
by robryk on Sunday September 25, 2016 @05:22AM
(#12574562)
> Any human being can tell you that DKTxHE is a bogus name for a function, so the only trick is to implement that detection in code...
Don't people run code obfuscators on macros?
Re:Investigating a malware sample which sometimes fails to b...
by jstanley on Sunday September 25, 2016 @06:16AM
(#12574677)
> the only trick is to implement that detection in code
String entropy scoring works surprisingly well for problems like this: build a corpus of function names (scrape it from github?), generate a markov model, see how probable the candidate function name is according to the markov model.
Re:Investigating a malware sample which sometimes fails to b...
by Senji on Monday September 26, 2016 @12:05PM
(#12582987)
Then I'll just run a prettifyer with the same sample data and name functions in my malicious macros from that.