Matt retweeted
This is a great analysis. I’ve developed similar ideas in our Christ-Centered Framework for using AI. brilliancelabs.org/aiframewo…
Matt retweeted
The collective intelligence of ants solving the “piano movers” puzzle.
📽️: Dreyer et al., PNAS 2025
🐕🪂 AIRBORNE K9s!
These military working dogs aren't just man's best friend—they're trained to jump out of aircraft alongside their handlers!
From the skies to the battlefield, these four-legged warriors are truly something special! 🇺🇸🐾
🎥 WATCH!
Noruega ya tiene más de 2.000 robots láser de IA submarinos disparando piojos de su salmón
los hace una empresa llamada Stingray, y ya protegen más de 50 millones de salmones y truchas las 24 horas del día
la razón son los piojos de mar, parásitos diminutos que se pegan al salmón y se alimentan de él
con tan solo 11 se puede matar a un pez pequeño, y un solo corral puede tener 150.000 salmones
la solución habitual es bombear los peces y lanzarles agua caliente o chorros de agua para quitarles los piojos
pero el manejo es tan brusco que el informe de salud de peces de Noruega lo señala como la principal causa de muerte en el salmón de granja adulto
así que en cambio, Stingray mete un robot dentro del corral que caza piojos de uno en uno, todo el día:
> dos cámaras vigilan cada salmón que pasa nadando
> la IA revisa dos fotogramas para asegurarse de que realmente es un piojo
> entonces un láser verde dispara desde hasta 2 metros de distancia
> las escamas del salmón reflejan el rayo, así que el pez sigue nadando bien y el piojo muere
ahora vivimos en un mundo donde los láseres de IA hacen control de plagas en tu cena lmao
Matt retweeted
i used fable 5.2 to make this "hand-painted" game in less than an hour
Every frame is about 1.5 million brush strokes, running at 200 fps in a browser tab. Open source too!
Matt retweeted
“Among gang leaders like General Barbecue there is a real concern about Bukele's no-nonsense approach to gang leaders like General Barbecue"
Matt retweeted
Binance published the postmortem on its $6.34 billion hack.
It started in June.
An engineer searched for an AI coding tool.
Downloaded a tampered Homebrew installer.
Binance caught it. Replaced the laptop. Rotated the credentials.
But the attackers had already learned who worked on the wallet team.
September.
A second engineer gets approached on a real job platform.
By someone posing as a project director.
Live video interview with "HR".
Then a take-home assignment.
Downloaded onto a work laptop.
The assignment swapped pyenv for a malicious copy.
Binance's security tools didn't flag it.
October 20.
The attacker used that machine and Binance's own internal AI tool to reach two more wallet engineers.
One had a container deployment token sitting on his laptop.
October 29.
Container deployed. Signing service reached.
Funds started leaving at 20:05 UTC.
Binance suspended withdrawals.
The money kept leaving.
The attacker had already authorized his own contract on the hot wallet, on-chain.
Halting withdrawals didn't touch it.
Revoking it was harder.
The wallet uses MPC.
No single private key exists to sign the revoke.
So Binance had to design a revoke procedure while the funds were still moving.
The last stolen ETH left almost four hours after the first transfer.
The security model designed so no one person could steal the keys.
Also meant no one person could stop it.
Binance says it recovered about 2.85 billion.
And put aside enough to cover the rest.
The FBI says North Korea did it.
Five months of recruiting, interviewing and waiting.
The most expensive take-home assignment ever submitted.
Binance just published how $6.34 billion walked out the door.
June: an engineer searches for a popular AI coding tool, clicks a search result, and installs a tampered homebrew. Binance catches it, replaces the laptop, rotates the credentials. the attackers now know who works on the wallet team.
September: another engineer gets a job offer on a real job-hunting site. first-round interview with “HR” over live video. “HR” shares their social media, personal photos and videos included, so he trusts them. second round is with the “CEO” of a company that doesn’t exist. at the end of the call he’s asked to download a take-home “assignment” onto his work laptop.
the assignment quietly swaps out pyenv for a malicious copy. No antivirus flags it.
october 20: the attacker uses binance’s own internal AI tool to get into two more engineers’ machines. One of them has a container deployment token sitting on his laptop.
october 29: container deployed. Signing service reached. $6.34 billion moved.
Binance shut off withdrawals. the money kept moving anyway, because the attacker had already given their own smart contract permission over a hot wallet, on-chain. binance’s off switch didn’t reach that far.
then they tried to revoke the permission. the wallet uses MPC, so there’s no single private key to sign the revoke with. they had to build a revoke procedure on the spot while funds were still leaving.
last stolen ETH went through at 23:56 UTC. almost four hours after the first transfer.
Phew!
Matt retweeted
This is horrifying.
JUST IN: French blood bank hit by cyber attack with blood samples being heated to 110 degrees Celsius from their maintained -30, per Le Canard Enchaîné.
Readers added context they thought people might want to know
The 110 °C figure was the value hacked equipment was reprogrammed to reach, which does not mean the cold rooms or plasma bags actually reached 110 °C. France's health ministry said the anomalies were spotted in time, with no operational consequences. cyberattaque.org/cyberattaque-c…
Matt retweeted
Dear VP Dumbledore,
We are eating plenty of candy. Tell Dobby to pick up the pace.
Love,
Potter and Malfoid
Matt retweeted
Not on my bingo card, but I’ll take it.
whitehouse.gov/briefings-sta…
Matt retweeted
I love how most of the animals stop running and look back at their saviors, its like an unspoken "Thank you, I will remember you."






























