2/ The investigation behind this Russian political interference takedown is interesting.
First, the @FBI got account registration info for a slice of fake accounts on @X
They found a lot of email accounts registered on the same server.
So they went to the registrar...
@FBI @X 3/ While the domain registrar (Namecheap) had a bunch of account registration information for the @FBI, the info was a fake name and some alias information.
Strike out? No. The FBI began a subpoena cascade, starting with the Google account used to register the domain.
@FBI @X 4/ @FBI had a tasty find from first gmail subpoena: Moscow IP address.
That was just the beginning: ubpoena cascade led through 2 more emails to a phone number.
Which they say they found in widely-leaked Russian tax & mobile subscriber information.
And got the operator.
@FBI @X 5/ Simultaneously, a jointly issued* a technical advisory provided detail on identifying Russian AI-generated personas.
Likely reflects their conclusion that the Russians won't stop.
☑️ Foreign efforts to shape Americans' perceptions via bots continue on @X despite Musk claims.
☑️AI is now a key disinformation op. tool.
☑️ Total # of accounts is small vs. @X universe, BUT doesn't rule out outside impact when well targeted.
7/ Cont'd:
☑️Takedowns & accompanying advisory suggest that US & allies are trying various techniques like these disruptions and seizures... because the operators are currently beyond their direct reach.
Expect the operators to learn, evolve & come right back targeting the US.
8/ Russia is one of many countries now swamping @X with AI-driven bots to shape perceptions.
Even smaller countries operations flourish & aren't taken down after being identified.
Want proof? Check the accounts in this campaign for yourself.👇
NEW: @WhatsApp caught & fixed a sophisticated zero click attack...
Now they've published an advisory about it.
Say attackers combined the exploit with an @Apple vulnerability to hack a specific group of targets (i.e. this wasn't pointed at everybody)
Quick thoughts 1/
Wait, you say, haven't I heard of @WhatsApp zero-click exploits before?
You have.
A big user base makes a platform big target for exploit development.
Think about it from the attacker's perspective: an exploit against a popular messenger gives you potential access to a lot of devices.
You probably want maximum mileage from that painstakingly developed, weaponized, and tested exploit code you created/ purchased (or got bundled into your Pegasus subscription).
3/ The regular tempo of large platforms catching sophisticated exploits is a good sign.
They're paying attention & devoting resources to this growing category of highly targeted, sophisticated attacks.
But it's also a reminder of the magnitude of the threat out there...
WHOA: megapublisher @axelspringer is asking a German court to ban an ad-blocker.
Their claim that should make everyone nervous:
The HTML/ CSS code of websites are protected computer programs.
And influencing they are displayed (e.g by removing ads) violates copyright.
1/
2/ Preventing ad-blocking would be a huge blow to German cybersecurity and privacy.
There are critical security & privacy reasons to influence how a websites code gets displayed.
Like stripping out dangerous code & malvertising.
Or blocking unwanted trackers.
This is why most governments do it on their systems.
3/Defining HTML/CSS as a protected computer program will quickly lead to absurdities touching every corner of the internet.
Just think of the potential infringements:
-Screen readers for the blind
-'Dark mode' bowser extensions
-Displaying snippets of code in a university class
-Inspecting & modifying code in your own browser
-Website translators
3/ What still gives me chills is how many cases surfaced of people killed by cartels... or their family members... getting targeted with Pegasus spyware.
The #PegasusProject found even more potential cases in Mexico.