We seeded 2m canaries into popular AI services and tracked where they were stolen and abused.
This identified:
- Three compromised providers
- Resellers stealing prompts via built-in logging
- Providers ignoring ZDR & privacy flags
dragos.com/blog/ai-supply-ch…
Aaronstotle retweeted
what the fuck is going on
We have discovered NGINX2Shell, a pre-auth RCE in NGINX 1.31.8, the current mainline release💥
This one came together in close work with @OpenAI, from discovery all the way through disclosure. Huge thanks to their team. More to come.
#NGINX2Shell
Shipping awful UX in software while existing in the era where you can point to an agent and say "fix this" makes it a nearly unforgivable crime
20
Aaronstotle retweeted
How I look at the fare evader while I wait to tap my card at the turnstile they’re trying to shimmy under
Aaronstotle retweeted
As a big 'monitor the situation' guy, there are currently way too many situations to monitor.
Aaronstotle retweeted
Fall Out Boy is bringing the Twilight Of The Punks Stadium Tour with special guests The Offspring, Good Charlotte and The Story So Far. Sign up now for presale access! 🤘
Aaronstotle retweeted
The bug is like a joke.
On Alpine Linux, type 257 to 1024 characters of anything and you get root. 💀
‼️ BREAKING: OpenSSH has rushed out a fix for a critical flaw that lets attackers log into some Linux servers without the right password.
The team learned of the bug a day earlier. OpenSSH's Damien Miller says long embargoes now mostly help attackers, because AI agents rediscover bugs, sometimes within hours.
It hits Linux systems on the musl C library with PAM off, such as Alpine Linux. Miller told admins to disable password logins or SSH itself "IMMEDIATELY".
Version 10.6p2 works around it. Systems on glibc or PAM are not affected, and Miller says the root cause sits outside OpenSSH.
Aaronstotle retweeted
someone that is at the Whitehouse between 5pm and midnight has some compromised devices.
Or at least some that are providing residential proxy access to botnets.
Aaronstotle retweeted
Replying to @thepunit
@thepunit Hi!
#Monero devs are trying for two weeks to enroll into Anthropic's OSS scanner, you're listed as reviewer on the PR: github.com/anthropics/oss-sc…
There has been zero feedback from Anthropic.
Any chance you could comment and help us move this forward? 🙏
What was lost: one of the UWS barn owl parents checking on their nest a couple nights ago (above) and doing the same with what little remained of it tonight (below). After a stressful day and early evening, the family reunited and all owlets were accounted for.
Cont’d
#birdcpp
Aaronstotle retweeted
Barn owl alert on UWS: Officers with NY Dept of Environmental Conservation as well as @bradhoylman & @NYSErikBottcher on scene as building workers appear to be back at the water tank that has been home
to a family of barn owls. Reporting @PIX11News
Aaronstotle retweeted
Looks like this was the largest exchange hack of all time with over $5B in assets stolen today from Binance hot wallets.
Crypto one again showing the revolutionary power of empowering North Korea
ok safe to say binance is pwned
The biggest assets were approximately:
• 1.615B USDT
• 62.6M RLUSD
• 29,934 wBETH
• 11,372 XAUt
• 6.19M UNI
• 198.4M ENA
• 7.175T PEPE
• 27.8M USD1
• 2.26M LINK
• 127,853 AAVE
about $2.5B at the explorer’s prices.
1. The attacker deployed a delegate contract, 0x63e842b0...73e9c6fAe, from the relayer at 15:59 UTC.
2. About four hours later, the relayer submitted an EIP-7702 authorization transaction
That installed the malicious 7702 delegate code on Binance 14.
3. The relayer then made a call to Binance 14, executing the delegate code, and transferring Binance 14’s ETH and token balances.
4. The calldata is labeled sweep(address, address[]). The second argument is a list of recognizable token-contract addresses plus the zero-address (eth).
5. The same relayer later used the same delegate to move 780M USDC from Binance Hot Wallet 34 into the same pool
• The relayer 0x7C... was funded by three Tornado Cash 0.1 ETH withdrawals over the prior two days.
• The same pool also received 28,005.6 ETH from Binance 16 24 seconds after the main sweep.
• The pool then forwarded 195,460 ETH to a fresh, unlabeled EOA
• That EOA has only one transaction and currently holds the 195,460 ETH.
What's a bit unclear is why the relayer was needed in the first place. If they had the private keys to the Binance wallets, they could have just sent the assets out in an atomic bundle without needing a relayer at all.
So it seems likely that they didn't have the private keys and instead just had the 7702 auth signatures, which must have been phished somehow.
I think we can go ahead and assume DPRK.
2
86
UPDATE: TOTAL BINANCE EXPLOIT TOTALS OVER $5.5B.
$2.29B in USDT (frozen), and $823M USDC (frozen).
18,270 BTC ($1.45B), 197K ETH ($451M) and about $730M of USDT has yet to be frozen.
Source: Hyperdash & onchain.







































