will strafach

2.1K Followers
442 Following
400 Posts
will (or @chronic on twitter). previously involved with some cool early iOS hacks and privacy research. started a company (acquired in 2022). now still hacking, researching, and angel investing.

New, from me: Who Operates the Badbox 2.0 Botnet?

The cybercriminals in control of Kimwolf -- a disruptive botnet that has infected more than 2 million devices -- recently shared a screenshot indicating they'd compromised the control panel for Badbox 2.0, a vast China-based botnet powered by malicious software that comes pre-installed on many Android TV streaming boxes. Both the FBI and Google say they are hunting for the people behind Badbox 2.0, and thanks to bragging by the Kimwolf botmasters we may now have a much clearer idea about that.

https://krebsonsecurity.com/2026/01/who-operates-the-badbox-2-0-botnet/

#infosec #botnet #IoT #Android #Google #threatresearch

The latest evidence that broadcasting people’s movements and intimate data in the Real-Time Bidding online advertising system is truly dangerous.

https://www.wired.com/story/ice-asks-companies-about-ad-tech-and-big-data-tools/

ICE Asks Companies About ‘Ad Tech and Big Data’ Tools It Could Use in Investigations

A new federal filing from ICE demonstrates how commercial tools are increasingly being considered by the government for law enforcement and surveillance.

WIRED

NEW, by me: A hacking campaign targeted high-profile Gmail and WhatsApp users across the Middle East this week, sent as a phishing lure over WhatsApp.

I obtained a copy of the phishing page and analyzed it with the help of experts. The attack aimed to steal passwords, hijack WhatsApp accounts, and grab victims' location data.

But a bug in the code also *exposed* victims' data, allowing us to see dozens of people who had fallen victim.

More: https://techcrunch.com/2026/01/16/how-a-hacking-campaign-targeted-high-profile-gmail-and-whatsapp-users-across-the-middle-east/

How a hacking campaign targeted high-profile Gmail and WhatsApp users across the Middle East | TechCrunch

The phishing campaign targeted users on WhatsApp, including an Iranian-British activist, and stole the credentials of a Lebanese cabinet minister and at least one journalist.

TechCrunch

🚨 Last call for our survey! 🚨 Are you a security researcher or journalist? We want to hear from you — please take this survey!

Dissent Doe at DataBreaches, and I, are running this survey to better understand the state of legal demands and criminal threats in cybersecurity.

Please help us by filling out this survey (and please share!)

https://forms.gle/yAiNNq2gTqE6ctWU8

Survey about legal and criminal threats experienced by journalists and security researchers

Researchers who try to responsibly disclose leaks, vulnerabilities, and other security breaches or mishaps may face legal threats or lawsuits. Similarly, journalists may find themselves threatened with lawsuits or other legal consequences if they report on leaks or breaches. Both researchers and journalists also face threats by criminals ("threat actors") if they report on them in ways the threat actors find unflattering or harmful. In our many years of reporting on leaks, breaches, and criminal gangs, DataBreaches.net and Zack Whittaker have often exchanged "war stories" about what threats we have received or had to contend with. After one particularly tiring week, we wanted to conduct a survey of researchers and journalists to ask about their experience with threats. We are using a broad definition of "researcher" to include self-defining or volunteer researchers (and not just academic or vendor-based researchers), as well as a broad definition of "journalist," to include bloggers and anyone who regularly reports on news and research, including commentary sites. Here are our questions, and we hope you will respond. Responses can be anonymous, but it will be helpful if you provide a real name or moniker and contact information, so we can follow up if we have questions. (Responses are encrypted in transmission and at-rest in line with Google's privacy policies. We plan to close this survey by end of day January 18, 2026.) Thank you for taking the time to complete this survey. (To report a survey bug, please reach out.)

Google Docs
iRobot apparently just declared bankruptcy, so if you have an internet connected one and want to retain control if the cloud platform vanishes, take a look at https://github.com/koalazak/dorita980#how-to-get-your-usernameblid-and-password and stash that information somewhere safe (and note that it changes if you ever factory reset the device, so try not to do that)
GitHub - koalazak/dorita980: Unofficial iRobot Roomba and Braava (i7/i7+, 980, 960, 900, e5, 690, 675, m6, etc) node.js library (SDK) to control your robot

Unofficial iRobot Roomba and Braava (i7/i7+, 980, 960, 900, e5, 690, 675, m6, etc) node.js library (SDK) to control your robot - koalazak/dorita980

GitHub

A nice post breaking junk hardware 🙂

https://blog.quarkslab.com/modern-tale-blinkenlights.html

A modern tale of blinkenlights - Quarkslab's blog

This blog post demonstrates how a modern variant of an hardware attack found in the 2000's allowed the extraction of a €12 smartwatch's firmware using only cheap and robust hardware. Damien and Thomas (introduced later in this post) gave a talk on this subject at this year's leHACK edition in Paris.

As a person who has followed Iranian cyberespionage operations for more than a decade, this story is crazypants and you should read it:

https://www.theatlantic.com/magazine/2026/01/mohammad-tajik-iran-cyber-intelligence/684954/?gift=kPTlqn0J1iP9IBZcsdI5IUTLJcsVKq12m0EyVlSYJBQ&utm_source=copy-link&utm_medium=social&utm_campaign=share

They Killed My Source

A man claiming to be an Iranian intelligence officer promised me he would reveal his country’s secrets. Then he disappeared.

The Atlantic

I've seen a number of people (including some well-respected people in the infosec sphere) promoting a particular blog post/writeup recently about the macOS secure boot chain. As someone who has done a fair bit of research and reverse engineering of iBoot and Apple's secure boot chain over the years, this naturally piqued my interest so I decided to take a look, at minimum to see how much it lined up with my RE of iBoot over the years.

Unfortunately after reading the blog post thoroughly, I can pretty confidently say this: the writeup is almost certainly a pile of AI slop. Let's dive into it and discover some major red flags that I found.

Let's talk about something that I think a lot of the people reposting this post haven't realized yet: this post was very factually wrong when it was first posted. (Here is a link to the earliest version on the Wayback Machine, very good resource btw ) Shoutouts to @nicolas17 btw for making archives once he noticed the article rapidly changing, he puts in a lot of work in the archival side of things that imo goes very unnoticed, but his work helps Apple security research in the long run.

This original version of the post has several factual errors (there are too many to list but some of the VERY obvious ones include Apple silicon chips starting at EL3 when no M-series Mac chip has implemented EL3 (which is optional per ARM spec) In addition there is contradictory info about the ECID, incorrect info on security fuses, etc, there's a LOT of slop to digest here along with tons and tons of jargon that makes no sense.)

The fact the post gets stuff wrong in and of itself is not the issue (a mistake here and there is completely understandable and in fact quite human), the issue is with the magnitude of how many factual errors were posted publicly, seemingly without any fact checking or sourcing, it really is quite egregious just how wrong this post is (even the current version of the post still has many of these errors), especially to any person who has even took a cursory glance at iBoot or the secure boot chain.

The syntax, per people I discussed this with, screams that it was based on prompting Claude (an LLM that seems to have more natural writing style than some of the others.)

However, what really is super insidious is the history behind this post. This is a link to diffs of the post over time, and it's pretty damning. The post had very very large chunks changed in very short amounts of time across multiple parts of the very long post, and with how long the post is, this is probably outright infeasible for a human to do in that short time frame (especially when incorporating time to fact-check the updated parts, which any writeup worth their salt imo should be doing.)

Per these two comments on HackerNews, along with the drastic changes mentioned before (especially considering that the post changed quite drastically between revisions, saved versions of which you can find here), it's pretty clear that what's been happening here is the person used AI to churn out this "writeup", then used the fact it was blatantly wrong to get people who knew how these systems actually worked to correct the post, and then told the AI to incorporate said corrections into the original post.

Let's be clear what's happening: the person is outright baiting people using this AI slop into correcting the post, incorporating said corrections without attribution to the people who corrected the post and then took the credit for said corrections silently. This isn't okay, this is a blatant abuse of community goodwill and the benefit of the doubt to fraudulently boost your own credibility and platform, without even a legitimate effort or attempt at doing proper research or fact-checking. (Not even diving into how LLMs are plagiarism laundering machines that yoink real human work and mash it together without any attribution.)

This "writeup" is nothing but of AI slop, and I strongly advise avoiding giving it attention. I'm very disappointed that people, even people I respect quite a bit, are promoting this like it's legitimate without reading it deeper and realizing this is AI slop.

Here are some writeups I strongly recommend reading, that have real, human, legitimate research placed into them:

A Reverse Engineer’s Anatomy of the macOS Boot Chain & Security Architecture

1.0 The Silicon Root of Trust: Pre-Boot & Hardware Primitives The security of the macOS platform on Apple Silicon is not defined by the kernel; it is d...

/dev/stack

I just published the slides of my #OBTS v8.0 talk about Apple's #C1 baseband. Our C1 #binja loader is now available on GitHub, and you can find a recording on YouTube.

https://lukasarnold.de/posts/obtsv8-talk/

OBTS v8.0: Diving into C1

Learn more about my talk “What’s at the Bottom of the Sea, One Baseband? - Diving into the C1” at eight edition of the Objective by the Sea conference.

Lukas Arnold

interested in working with very unique and high volume network data to discover emerging threats? come work with me at DNSF!

http://job-boards.greenhouse.io/dnsfilter/jobs/4944382007

Director, Threat Hunting

United States