Decker retweeted
KEYSTONE TO DESTROY 18,835 HARDWARE WALLETS AFTER HACKERS STEAL DEVICE AUTHENTICATION KEY
Keystone has confirmed it will destroy 18,835 hardware wallets in existing inventory after attackers stole the cryptographic key used to verify the authenticity of its devices.
The breach is particularly concerning because the stolen key could allow attackers to manufacture counterfeit Keystone wallets that successfully pass the company's official authenticity checks, potentially putting users' Bitcoin at risk.
The key is permanently embedded in existing devices and cannot be erased or replaced, forcing Keystone to destroy its remaining inventory, suspend shipments and manufacture new devices with a replacement key.
The company says attackers exploited a vulnerability in a third-party monitoring tool on its official website on October 20, gaining access to:
- 25,964 customer records containing names, contact details, shipping addresses and purchase information.
- 12,873 abandoned checkout records containing potentially sensitive customer information.
Keystone also acknowledged that its automated data deletion system had failed, leaving customer information stored beyond its stated retention period.
The company says recovery phrases, private keys and transaction signing were not compromised.
Devices delivered before October 20 remain unaffected, but customers receiving devices with the old authentication key after that date are advised to seek additional verification.
Keystone has suspended shipments, begun notifying affected customers and is moving production to a new authentication key.
banned for reverse engineering work? that’s wild
oh well, -$500, and a bunch of banked resets) but gained motivation to get 3 more machines and finish my cluster.
i have never used openai to exploit or find vulnerabilities, only local reverse engineering which tripped daybreak.
Today's combo:
• PHP: two critical unauthenticated RCEs.
php.net/archive/2026.php#202…
• Node.js: RCE + TLS validation bypasses.
nodejs.org/en/blog/vulnerabi…
• eMudhra: a CA private key was literally 4.
theregister.com/security/202…
What's next? SSH authentication by vibes?
Decker retweeted
The end of software secrecy is almost upon us. The death of closed source, and the final triumph of open source.
I should have realized this a few months ago when I successfully decompiled the game of Firefighter from an ancient DOS shareware binary. My robot friend was able to tell it had been written in Borland Pascal from looking at the data layout; it gave me back very readable Pascal code with sensibly chosen function and variable names. I transpiled it to Rust and now ship it as part of my heritage games collection.
The thing is, I thought of this as a fun stunt but didn't have any confidence that the technique would scale up to large, real programs. I have since learned that people are now doing this sort of thing with entire AAA games, which are among the most complex software artifacts ever to be shipped as a binary. If they can be decompiled, anything can be.
This has implications. Massive implications. We need to think about what the world is like when, in general, there is no longer a secrecy moat around almost any software at all.
1/2
Decker retweeted
Cloudflare CLI is now in beta. It unifies Workers, DNS, and security management into a single tool that works great with coding agents.
developers.cloudflare.com/ch…
Decker retweeted
The era of new technologies obviously needs a new kind of money. Banks and money in general now feel like using a horse to commute in a megacity 🐴
decker.im/recover-forgotten-… - How to Recover a Forgotten Password in a Mikrotik CHR Instance on a VDS
#MikroTik #RouterOS
blog.cloudflare.com/next-git… - Cloudflare is hosting a competition to see who will build the next Git platform for an era of AI agents. Artifacts is in open beta, with Workers bindings, data jurisdiction controls, and event subscriptions for repository changes.
Got a WinBox Addresses.cdb and need your saved MikroTik logins out of it? 🔑
WinBox CDB Viewer: a small open-source Rust app to view the address book and export it to TXT/JSON. Password-protected books supported.
Linux & Windows 👇
github.com/DeckerSU/winbox-c…
#MikroTik #WinBox #RouterOS #Rust
You know those hacker movies I laughed at as a kid?
The ones where a guy types into a console, literally: "Now let's figure out the encryption algorithms our binary uses and try to decrypt the config as it was saved to NVRAM"... and the computer chugs for a bit and hands him back AES-128 CTR with the key right there.
Turns out that was all real. No reason to laugh at all.
The magic words? Ghidra + GhidraMCP. 🔥
Decker retweeted
Put together a complete walkthrough for deploying WireGuard and Pi-hole in Docker using a private internal bridge network (172.28.0.0/16) so clients can never bypass ad-blocking. Full Guide:
techloverhd.com/2026/09/buil…
#WireGuard #Pihole #Docker #SelfHosted #Homelab
Here's what I call "good marketing"... in the package with the hardware wallet they included a card advertising their LedgerCL card.
@Ledger
It's actually so cool when your AI agent controls GitHub via the API, launches a workflow on a self-hosted runner based on a Mac M2 that sits literally to your right but without a monitor... automatically gets the workflow execution results through gh run view... and fixes the workflow itself if something is wrong with it... and so on, iteratively...
Decker retweeted
BREAKING: shielded Zcash is now supported in @Ledger Wallet.
Decker retweeted
Opus 5.5 designing LEGO 👀
I asked it to design a Microduck I can build with real LEGO pieces. It:
> designed it life-size using 1113 real LEGO parts
> verified: 3,204 connections, 0 collisions, every step buildable, centre of mass inside the feet 🤯
> made a 141-page LEGO-style booklet (237 steps)
> priced every piece in the browser and prepared the orders on BrickLink
When Codex doesn't want to check the safety of the rules that it just created itself, all within a single prompt... =)
At the moment I'm hardening the security of one of my web projects. Absolutely everything is deployed in a local Docker, I'm adding new security rules and asking it to check them automatically. But the security subsystem won't let me do this, because the rules turned out to be too complex. If you lower the complexity of the rules - in other words, if you make the security worse - then it checks them. But really secure configurations, even ones created with Codex itself, it doesn't want to test )) So OpenAI is encouraging us to create less secure configurations. Perfect. Actually, no.

















