My spy-implanted ledger came from Malaysia, and had flawless shrink wrap. Even opening it, at first you don't see the implant which is cleverly hidden where the screen's padding is supposed to be. Follow Ledger's guidance to check yours: support.ledger.com/article/4…

In August the Core Lightning maintainers told node operators to upgrade or run --offline. There was nothing to upgrade to for another two days, and when v26.06.7 arrived it was binaries only, with the source held back a further two weeks so attackers could not reverse-engineer the fixes. We (me + AI models) used that window. Ten AI models, one public source tree, the same five sentences of prompt, under $100 between them. Every report was hashed into the Bitcoin blockchain with OpenTimestamps as it was finished, nine days before upstream published the source, so none of it can be backdated. Reading source, the models found four of the nine defects the release fixed. Running "strings" on the public download found five more, and one of those is theft that pays for itself: as a forwarding node you refund the sender upstream, and the peer then claims the outgoing HTLC on-chain with the preimage it held the whole time. You pay twice and collect nothing. It was findable because the patched binary carries upstream's own new log line, FUNDS LOSS, which names the function, and the vulnerable code sat in the public v26.06.6 tree throughout. Three models at three price points landed on it within minutes of the download. The embargo hides the patch, but not the mechanism. Write-up: juraj.bednar.io/en/blog-en/2… Full case-study, reports and timestamps: github.com/jooray/CLN-incide…