News for hackers. Stuff that matters.
Re:Investigating a malware sample which sometimes fails to b... by meowface on Sunday September 25, 2016 @01:54AM (#12574168)
This has become really common. Most modern malware sandboxes attempt to greatly accelerate the system clock to account for this, in addition to trying to detect and intercept long sleep (or equivalent) calls.

Like most long cat-and-mouse games, modern malware families all use a combination of many different tricks and anti-sandbox/analysis techniques. The sandboxes play whack-a-mole at the same rate as malware keeps adding more moles.

Re:Investigating a malware sample which sometimes fails to b... by Tinyyy on Sunday September 25, 2016 @02:16AM (#12574226)
If the malware attempts a CPU test that maxes out the host CPU, will it be obvious that the system clock is sped up?
Re:Investigating a malware sample which sometimes fails to b... by cnvogel on Sunday September 25, 2016 @09:03AM (#12575130)
So… only speedup the clock while the software under test is sleeping (waiting on a muted, timer,…) . Stealthy software shouldnt have excessive cpu consumption, otherwise people will investigate.

It's obviously a cat & mouse game.

Re:Investigating a malware sample which sometimes fails to b... by Senji on Monday September 26, 2016 @12:06PM (#12582993)
I propose a scorched earth tactic. Refuse to run unsigned code.