I was repeatedly targeted by the threat actor from December 4th until January 24th. I never received any LPE. It surprised me so many people did, given the context. I’d like to offer some non-technical advice on how you can avoid becoming a victim of this specific type of attack:
First, the lure was the ask of advice on weaponizing a DirectX Kernel 0day exploit.

Unless you know a researcher, it seems like a dubious choice to advise in the exploitation of an 0day. You never know what they’re going to be doing with it.
Secondly, given that nobody knew this researcher, I was shocked some people showed willingness to help.

Consider: how do you value your time and what was the intent of this 0day?

If you’re in the business of exploitation, giving an unknown actor free 0day help seems dangerous.
Now I know many folks here choose to engage in this line of work. That’s fine.

My next advice is around opsec.

Someone is offering you a free LPE because “they trust you”. Really? Someone you’ve never met “trusts you”? Does it not perhaps look like an ego lure for an 0day?
But say you fall for it, and someone is “trusting you” and giving you an 0day.

I repeatedly refused communication unless it was encrypted. The threat actor suggested all sorts of unencrypted or open channels that are dubious and unverified. They kept wanting to email me a ZIP.
If you’re in the business of giving free help to unknown researchers that are giving you 0day because “they trust you”, consider not relying on encrypted zip files.

Validate your other party. Phone, video, Skype, authenticated encrypted communication.

Not a ZIP file by email.
Because at the end of the day, whether you were just curious, or were hoping for a free 0day, or are just altruistic and wanted to help a fellow human, or ..., next time sometimes offers you a free 0day and you download a zip file by email — it won’t be a poorly run campaign.
Stay safe, friends. The world is a dark & scary place. Nothing comes for free, and when it does, there’s usually nothing good that comes with it.

You’re all talented, helpful, smart folk, regardless of your alignment on the exploit business spectrum — don’t fall for free 0day 💜
Some will choose to read this as “I’m better than you because I didn’t get phished”. I’m not. I fall for lures all the time. I’ve even run RATs on my system before. Others like @halvarflake didn’t fall for this either. I’m sharing what was successful for me, in this context.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Alex Ionescu

Alex Ionescu Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @aionescu

25 Apr 18
1/ Of all the weird stuff I have ever seen Win32k.sys do, and trust me, I've seen a lot, I have to say this takes the icing on the cake. This is now all over it. Is there a new dev team that does't understand how (why?) the code base works? Is someone desperately hunting a bug? Image
2/ I am a huge fan of assertions -- use them all over the place. But _runtime_ assertions, with textual strings which send a live crash/telemetry back to the developer? They also happens to basically provide a guided map to where the bugs are. I love seeing words like "should".
3/ Well, I guess this is what happens when you no longer really ever build/use checked builds (apart from some teams) which had ASSERT_MSG providing similar behavior, and don't make them avaialble for customers anymore. Now you have them in retail builds causing live dumps.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!