Zvn retweeted
I was able to decompile and analyse 494 wallets on the AppStore.
I found 45 apps that raised red flags for me during my research.
I looked specifically for 2 things: private keys exfiltration and weak entropy.
Zvn retweeted
“The breach is limited due to Trezor’s strict 90-day data storage policy”
Not good. But kudos to Trezor for limiting the damage with this policy.
We have some difficult news to share. Unfortunately, one of our shipping providers has experienced a data breach that exposed sensitive order data. This affects new customers in the US, UK, Sweden, Colombia, Brazil, Italy, and Portugal who received an order within the 90 days prior to August 8th, 2026.
The data exposed:
- Full names
- Shipping addresses
- Phone numbers
- Email addresses
The incident affects 11,742 customers with full exposure (name, email, phone number, shipping address) and 1,947 customers with partial exposure (name, city, email). The breach is limited due to Trezor’s strict 90-day data storage policy (we were also able to negotiate the same terms with fulfillment partners, who follow the same policy).
All affected customers have been contacted separately by email.
Our systems and devices remain secure, but affected customers could experience an increase in phishing attempts.
NEVER enter your wallet backup on a website or share it with anyone, and only check for updates on official Trezor channels.
We are deeply sorry to the community and those affected.
We are investigating this situation and will post updates on our blog:
trezor.io/blog/news/recent-c…
Zvn retweeted
This should be the absolute default for bitcoin-sensitive deliveries.
We are currently working on an Anonymous Delivery option, which we aim to have ready by September for the EU and by the end of the year for the US.
This gives you a safer way to order hardware wallets without linking the purchase to your home address or real-world identity.
- Dedicated checkout
- Use a nickname or label ID
- Select an automated parcel locker for pickup
- Unbranded packaging with a generic sender label, while the carrier only uses email or SMS to send a pickup PIN
This project is a top priority at the moment.
Zvn retweeted
Great writeup @opchecksig I'm really impressed with the thoroughness and nuance you captured. Just a couple of corrections.
6.5) Trusted contacts and inheritance beneficiaries are identifiable (subpoena-able) and individually coercible humans holding key shares.
There's no identity associated with TCs and Beneficiaries beyond the nickname entered into the mobile client.
7.2.1) Store the Emergency Exit Kit PDF offline, separated from the hardware device. EEK plus hardware is a quorum; their separation is the control. (4.2, 5)
You should be sure to update the physical copy after key rotations (recovery)
7.3.1) Generate the Emergency Exit Kit now. It covers loss of the phone without any cooperation from Block. (4.2).
The EEK is generated automatically during onboarding and updated every key rotation.
7.3.3) Archive the emergency APK and its embedded hash while things are calm, and know how to sideload it before you need it. (4.4)
You can also do an exit with your own custom built software, I was able to one-shot it with an LLM prompt I plan to share publicly.
Finally
One other thing the report is missing is that when you buy the hardware, you can pay in bitcoin and deliver to a public pickup point, removing identity information associated with payment method or address. I think this is relevant to points 1.7, 4.3 and 7.1.6
Zvn retweeted
Also interestingly, doc-hex who we now know he's the author of both repos correctly implemented the "if MICROPY_HW_ENABLE_RNG" for ckcc.random, but made a mistake in libngu which caused the vulnerability
Zvn retweeted
I find it interesting because ckcc.random is still in the firmware to this day, and it's used in a few other places. Only the seed generation was migrated from ckcc to ngu
Zvn retweeted
what is happening now for the bitcoin industry is a preview of what will need to happen for every other industry in the upcoming months
it's starting with bitcoin because:
- this is where there is the most immediate and transferrable asset to steal from.
- the security posture of most repos/projects have not caught up with the open source model capability.
but when the low hanging fruits are gone (ie: k3 just doesn't find vulnerability anymore by simply pointing it out in a github repo), then the blackhats will mostly move elsewhere
Bitcoin Red Team Update:
We have been working around the clock, with ~$20,000 of spend up to this point across different services. Funding is secured, I appreciate all the gestures for donations but it is not necessary. The bill is taken care of.
We have done over a dozen disclosures up to this point, with 150 repos scanned. The hardest part is coordinating to get things to the right people (thank you @danielabrozzoni for the help)
I have a first pass on a bitcoin red team agent harness which only requires an @opencode zen api key, makes it easy for us to use K3 for the actual heavy lifting and then GPT Sol + Fable/Opus + GLM5.2 for supporting documentation.
While it is powerful, having found critical issues, I would view this as only version one. There is a lot of iteration I'm looking forward to improving on.
Our goal is to open source the harness so it can be pointed at internal repositories for insights so the hardening of defenses can go deeper than the code which is made public.
We also have been connected with OpenAi for some help so I could manage getting the @OpenAI Cyber Harness running as well (thank you @lylepratt ). Its a much more expensive scan, but well worth it for load bearing portions of the bitcoin ecosystem and has already yielded good results.
Goals for tomorrow are scale in processes and systems so we can do a better job and automating full end to end functionality to get humans out of the loop for the heavy lifting. The first mile (requests/staging) and last mile (handoff of reports) are the choke points right now.
Thank you @stutxo @callebtc @benthecarman @thesimplekid and so may more.
Zvn retweeted
Tldr for scared people:
1) If you have significant money on keys generated by a ColdCard Mk3 without proper dice rolling and without a strong passphrase, MOVE THEM NOW, even just to a hot wallet, while you fix your cold setup (if your hot device is compromised you may lose funds anyway, but if you leave them there you most likely will pretty soon, so don't wait for the perfect setup to move, move now and perfect later).
2) If you have significant money on keys generated on a more recent ColdCard, or on a Mk3 with a very strong passphrase, or in a MK3 multisig you didn't spend from yet, you have more time. Take a few calm, focused hours in the next few days, create a good setup, understand it, test it, and then move. Mind privacy, even if it may seem the least of your concerns now. I personally use a 4-layer segregation between phone LN wallets, a LN node, a JAM wallet, a cold setup with decreasing threshold 3/3 multisig with Liana: a old laptop with Tails with persistent storage on Electrum, an old Ledger NanoS, a ColdCard Q, in all 3 I generated entropy externally with cards, the other seeds generated from the ColdCard with BIP85. There's no one size fits all.
3) If you don't use ColdCard, it's still a good occasion to review and improve your setup. Use multisig with different vendors to spread out the risk. If you have money on exchanges, the very same LLMs that found this will also find vulnerability in those massive honeypot. Take your money away from there asap.
Zvn retweeted
$BTC
Closed at $60k support
There is a world in which something goes terribly wrong and we wick towards $45k this month
If so it's a buy IMO
If not 60k seems good
I bought a little bit at support a while ago
Will add big if $45k happens
Will add smol if we reclaim mid 60s
Zvn retweeted
The zero-interest-rate era is going to become lost history because people want to make up a narrative around AI. The white collar bloodbath didn't happen because of a chat app release, it happened because of the end of ZIRP which occurred rapidly in 2022.
Zvn retweeted
Are you considering running a Bitcoin Knots node? It's fully within your right to do so.
But if you do, you should be informed of what you're getting into.
blog.lopp.net/knot-a-serious…
Zvn retweeted
Ross was just granted a FULL AND UNCONDITIONAL PARDON by @realDonaldTrump. Words cannot express how grateful we are.
President Trump is a man of his word and he just saved Ross's life. ROSS IS A FREE MAN!!!!!