Pinned Tweet
when BOJ rug pull America?
How many more chips would be purchased in USA if there was a moratorium on serving inference models from datacenters? 2-4yrs long? How would that shift demand for GPUs?
The emergency test proved that the system is inept at capturing the attention of much of the population through amplified/elevated noise of a fall Tuesday
Those who knew about the test knew it was happening through alternative channels
To be clear, today’s emergency alert was not intended to test whether humans could be reached. It was a technical test of the broadcasting infrastructure.
At 2:20 p.m. in New York and 11:20 a.m. on the West Coast, the federal government tested its national Emergency Alert System across television, radio, cable and satellite services. Cell phones were deliberately excluded.
On a Tuesday afternoon, when millions of Americans are working, attending school, commuting or otherwise nowhere near a television or radio, who exactly was this test designed to reach? Stay-at-home parents, retirees, hospital patients, nursing homes and whoever else happened to be watching television or listening to the radio?
In New York, it was the middle of the working afternoon. In California, it was 11:20 in the morning, with much of the population at work or in school.
The government may successfully demonstrate that an alert can be transmitted across the broadcast infrastructure, but it does not establish how many Americans actually received it, noticed it or would know what to do in a real emergency.
The failure here is in the design of the exercise, not necessarily the technology. We can declare the transmission successful without knowing whether the population was effectively reached.
In an actual national emergency, the number of Americans who never receive the warning may be considerably more important than the number of broadcasters who successfully transmit it.
That is what should be tested.
3
4
198
People have wanted to solve the spam phone call problem for 10yr+. It costs American's billions $ per year. It is a legitimately difficult problem to solve
Agentic attack/probe campaigns are worse. It'll cost an order of magnitude more billions $. This problem harder to solve
3
5
360
This is a Franz Ferdinand moment
xitter.gq/mgogel/status/14361970…
Ledger is officially a villian of private selfself-custody principles.
Follow up: I found something even more absurd ⚠️
Since context-module 2.7.0, Ledger's SDK sends a SECOND report on every signature, to /v2/blind-signing-events, now with the function selector too.
It's on by default, and unlike v1, the SDK gives no option to replace or disable it. So any wallet that turned off the v1 report starts sending again after a routine update.
Their signer kit changelog says it plainly: "Require context-module 2.7.0 (sign reporter enabled)"
github.com/LedgerHQ/device-s…
github.com/LedgerHQ/device-s…
Alongside @ambire, @Rabby_io also caught the v1 report from my post below 👏 They replaced Ledger's v1 reporter with a local callback that sends nothing:
github.com/RabbyHub/Rabby/bl…
But they're still on 2.1.0, which has no v2 reporter yet. The day they update, v2 goes out anyway unless they catch it. So heads up, fellow wallet devs: the builder has no setter for the v2 reporter, so you need to gate `signReport` on the built module yourself.
Ambire is safe because we're not on 2.7.0. Since Ledger gives no setting for the v2 reporter, our next SDK update overrides it in code, so it follows the same opt-in privacy toggle we already use for v1 (off by default).
@Ledger, is this a test to see if we're paying attention?
I guess at this point we should review every SDK update line by line.
1
1
79
Replying to @DonjonLedger @BitcoinNewsCom
This is simply not true: blind-signing.api.ledger.com has nothing to do with resolving ERC-7730 descriptors.
1/ Descriptors are fetched in the BuildContexts step, BEFORE the user signs. The report is a separate DetectBlindSigning step that runs only AFTER the device returns a signature. It even runs when the user rejects on the device. At that point there's nothing left to resolve:
github.com/LedgerHQ/device-s…
2/ It's a fire-and-forget POST to /ingest/v1/blind-signing-events with responseType: "void". The response is thrown away, so it can't be feeding any descriptor lookup:
github.com/LedgerHQ/device-s…
3/ Payload: chainId, contract/recipient address, device model, firmware version, Ethereum app version, isBlindSign + reason. Firmware and app versions don't help anyone find a descriptor:
github.com/LedgerHQ/device-s…
4/ It fires even when NO descriptor was found. That's literally what isBlindSign: true means. And it fires without an originToken, which your own docs say is required for Clear Signing.
5/ Your own PRs call it a "blind signing reporter" (#1389) and "Multichain blind-sign tracking" (#1966), not descriptor resolution:
github.com/LedgerHQ/device-s…
github.com/LedgerHQ/device-s…
Since context-module 2.7.0 there's even a second (v2) report per signature, and the builder has no setter to swap it out.
"Integrators control it" only helps if they know it exists. It's on by default, and neither of the two docs pages you linked mentions it.
Privacy should be opt-in, not opt-out!
20
Signal protocol formally verified by DeepMind
It's easy, use Signal
deepmind.google/blog/introdu…
2
81
there is no shelter
A vulnerability (worse_query) affecting iOS 26.7.1, 27.0.1, and 27.2 allows malicious apps to read local files from other apps, putting seed phrases, private keys, and login credentials at risk across the entire ecosystem. This is an iOS-level issue, not unique to Binance.
Immediate Action Required:
- Delete any apps installed from untrusted sources (such as sideloaded or manually signed IPAs).
- Update iOS and all apps to the latest official versions.
- If you suspect a breach, transfer funds to a new wallet created on a clean device and reset all active login sessions.
Never install unauthorized packages, and keep your software up to date.
Readers added context they thought people might want to know
Binance recommends updating iOS to the latest versions against worse_query, but researchers describe it as an unpatched 0day and Apple's iOS 27.2.1 notes omit any such fix.
github.com/forcequitOS/wo…
support.apple.com/en-us/149715
x.com/0xjohnny/statu…
53
where did Anonymous go?
Remember, remember the fifth of November.
Given my habit, and just maybe, maybe my reputation for speaking to invisible audiences, nobody would ever put it past me to address the members of Anonymous, everyone who has ever worn the mask, everyone who marched in the Million Mask March, everyone who still believes in the Idea, those who stood against the abuse of power, those who disappeared, those who remained, those who went silent, those who are still listening, the real ones, the old ones, the ones no longer with us, the ones we still have, those who, regardless of their goals, find commonality in that same je ne sais quoi, and everyone who never knew who was standing beside them, like shadows.
I send my regards. I write this one to you.
It’s been a very long time.
Remember, remember the fifth of November.
Sup! Hi lol, or should I say lulzzz.
Good news with the midterms. Anywho. Tomorrow’s another day.
Good luck in whatever it is you do, whoever you are, and wherever you are.
Mike. I’m still me. :)
1
2
96
If this hack has key compromise, it makes me wonder if the derivation originates from the same source
1
57
GCP and AWS are having issues meeting demand; they are at capacity for compute.
when the cloud can't scale on demand, what happens?
vulnerability disclosure is the weapon
You won’t read about this anywhere else because it’s a theory. A very very good theory.
PHP2Shell: What if the disclosure was part of the operation? High-level cyberwarfare ahead of the next phase of the Iran war.
On October 18, technology-tracking service Aguko identified 138,595 Iranian .ir websites using PHP, representing 96% of Iranian websites with an identified server-side programming language in its dataset.
Consider the possibility that the October 2026 PHP2Shell disclosure was neither an accident nor simply a cybersecurity emergency, but an event whose timing could serve a broader intelligence operation against Iran.
This is an insane concentration of exposure to a common technology. It does not mean that 96% of Iranian websites were vulnerable, but it establishes how extensively PHP is embedded in the country’s publicly visible digital infrastructure.
The vulnerabilities were not confined to an obscure plugin. They existed within PHP itself, affecting versions spanning more than a decade. Successful exploitation under the right conditions could allow unauthorized code execution, access to sensitive information, and compromise of affected servers.
Now consider who discovered them.
In August 2026, Wiz Research, part of an Israeli-founded cybersecurity company acquired by Google, independently identified critical PHP vulnerabilities. Wiz’s founders previously served in Israeli military intelligence, including Unit 8200, the intelligence organization historically linked to Stuxnet, the cyberweapon that sabotaged Iran’s uranium-enrichment centrifuges.
Other independent researchers, including Calif and OpenAI, also contributed to discovering and reporting the vulnerabilities. The military backgrounds of Wiz’s founders establish a historical connection, not evidence of involvement in a contemporary intelligence operation.
Still, the chronology becomes more interesting.
October 17: Amazon detects an attempted exploitation of PHP2Shell through its MadPot honeypot network. The activity originates from anonymized infrastructure, four days before the official public disclosure. Amazon cannot establish how the actor acquired knowledge of the vulnerability.
October 18: Aguko’s dataset places PHP’s market share at 96% among Iranian .ir websites with an identifiable server-side programming language.
October 20: Confidential vulnerability identifiers begin circulating publicly. A demonstration video is prematurely released. The PHP Foundation accelerates its disclosure timetable. Mitigation information shared with some critical-infrastructure providers may also have leaked.
October 21: Patched versions arrive. One vendor publishes patched software more than six hours before the agreed release, while researchers observe exploitation attempts and the internet begins responding to a global security emergency.
Someone was attempting exploitation before the vulnerabilities were supposed to be public. The origins of that knowledge remain unresolved.
Now consider the military significance of the sequence.
Modern cyberwarfare does not necessarily begin with an attack on the ultimate target. It can begin with intelligence collection, access to peripheral networks, mapping of dependencies, compromise of suppliers, and the positioning of capabilities that may become useful later.
An adversary seeking to disrupt a nuclear program would not necessarily need to begin inside a centrifuge facility. The broader technological ecosystem includes administrative services, engineering organizations, research institutions, contractors, procurement channels, communications, and other systems that may hold information or maintain connections of intelligence value.
A vulnerable PHP installation could theoretically provide an initial foothold somewhere within that ecosystem. Reaching industrial control systems would require additional access and capabilities that have not been demonstrated in this case.
offline movement is growing
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
About how many routers running php servers will go unpatched?
‼️BREAKING: PHP has released its fix for the two leaked flaws, which can let attackers run code on servers without logging in.
"There are no complete mitigations, updating is the only safe choice," PHP says.
Update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 now.
PHP says Apache with mod_php is most at risk, with a demonstrated exploit that fires before any application code runs.
PHP 8.1 and older get no official update, though PHP has published source backports for 7.4, 8.0 and 8.1.
1
99






































