Bitcoin Hat Guy🧢 (@knowbitcoin) header
Bitcoin Hat Guy🧢 (@knowbitcoin) profile picture

Learn about bitcoin. Bitcoin hats since 2013 Hats embroidered in house I sell Bitcoin Hats for Bitcoin Need custom hats or want to buy in bulk, DM me

California
Joined October 2013
Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)Photo by Bitcoin Hat Guy🧢 (@knowbitcoin)
Bitcoin Hat Guy🧢 retweeted
📢 Our incident response investigation identified an attack vector targeting instances running versions 2.4.1 (Jul 23, 2026) or older. We have no credible reports of hot wallet drains for users running the latest 2.4.7 release. We again urge everyone to keep their BTCPay Server updated. If you were impacted, please send all details and logs to [email protected]
29
102
54
237
41,295
Bitcoin Hat Guy🧢 retweeted
An all time X response.
219
1,703
110
31,596
881,644
Bitcoin Hat Guy🧢 retweeted
Update on my part: Our public servers were not attacked (on 2.4.7), it seems reports are on before 2.4.2. The attacker managed to log in as admin on those instance, we are still trying to figure out how.
🚨 We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers. If you're running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.
14
20
12
91
6,651
Bitcoin Hat Guy🧢 retweeted
Not a drill: shut down your BTCPay Server if you have a hot wallet. Appreciate the reposts 🙏
🚨 We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers. If you're running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.
23
286
21
577
59,094
Bitcoin Hat Guy🧢 retweeted
🚨 We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers. If you're running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.
265
1,052
440
2,991
749,468
Bitcoin Hat Guy🧢 retweeted
Binance has begun recovering affected assets for users and continues to work with law enforcement, issuers, blockchain intelligence firms and industry partners to trace, freeze and recover additional funds. The company has already publicly committed to cover losses through company funds in the prior announcement. Binance has already reserved over $6.34B of company funds to cover this incident. $5B of these funds are already held in the exact token assets that were impacted. We are completing the purchase of the remaining amount by buying token assets through market channels and OTC channels. We are doing this to match the format of the remaining token assets and address any asset shortfalls. This step can take longer because some tokens may have low liquidity and OTC settlement also takes time. We will share more progress as soon as we can. These figures do not include frozen or protected assets, which remain subject to ongoing recovery and verification. Currently, $3bn has been frozen, with thanks to our industry partners. We are working with partners and law enforcement to recover the frozen assets.We will continue to use company resources to cover confirmed shortfall and will provide further verified updates as recovery efforts progress. Ultimately, all user funds will be verified publicly through our Proof of Reserves. We will weather this storm. Thank you for the support.
1,413
1,736
608
11,434
3,000,693
Bitcoin Hat Guy🧢 retweeted
At midday yesterday, I kicked off an initial blockchain download using the newly released Bitcoin Core v32.1. I woke up this morning and it was done. It took ~18 hours all up. Specs: Dell Optiplex 7050 i5-7500T 8GB RAM 2TB Samsung 870 EVO 1000mbps connection
16
15
1
142
7,901
Bitcoin Hat Guy🧢 retweeted
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified. The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete. As an immediate precaution, Binance has: - temporarily suspended deposits and withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds. Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice. Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions. binance.com/en/support/annou…
3,430
6,176
3,758
29,654
7,098,080
Bitcoin Hat Guy🧢 retweeted
Update: The current verified total frozen amount is around $3 billion. Our teams continue to work closely with law enforcement, issuers, blockchain intelligence firms and industry partners to trace and freeze additional assets. We will only share confirmed figures and will provide further updates as more verified information becomes available. User funds are safe.
542
672
294
4,126
1,405,484
Bitcoin Hat Guy🧢 retweeted
Binance theft thread of data 👇
1
16
1
47
10,304
Bitcoin Hat Guy🧢 retweeted
It’s looking like Binance had one master key for all of their hot wallets across all chains. Pretty insane.
76
80
30
1,221
64,184
Bitcoin Hat Guy🧢 retweeted
BREAKING: Binance has been hacked with wallets across the Ethereum, Bitcoin, and TRON networks seeing outflows of -$5.7 billion. The hack includes $1.45 billion worth of Bitcoin and $875 million worth of ETH. If confirmed, this would mark the biggest hack in crypto history. We expect more information shortly.
1,252
5,133
1,992
37,016
9,697,027
Bitcoin Hat Guy🧢 retweeted
ZEUS v13.2.4 is now available. v13.2.4 Highlights: - Embedded LND v0.21.5-beta - LDK Node v0.7.1 - CDK v0.18.2 - Further security hardening measures - Miscellaneous bug fixes - Miscellaneous UI improvements
2
12
49
2,501
Bitcoin Hat Guy🧢 retweeted
🚨 We're releasing BTPay Server 2.4.7 an emergency update fixing one critical and several medium-severity security vulnerabilities brought to our attention through @Anthropic's frontier OSS scanner. We recommend that you update your BTCPay Server as soon as possible.
13
111
16
224
28,797
Bitcoin Hat Guy🧢 retweeted
Sparrow v2.5.6 has been released, removing the eMudhra root certificates and upgrading the bundled Tor to meet the client protocols now required by the Tor network. It also brings extensive screen reader and keyboard accessibility improvements. Changelog: github.com/sparrowwallet/spa… Download: sparrowwallet.com/download
Sparrow v2.5.0 released with: Silent Payments (SP) wallets SP-capable Frigate public server @2140_dev bitview.space fee rates source sparrowwallet.com/download
21
166
10
850
31,229
Bitcoin Hat Guy🧢 retweeted
Saying there’s no reason to buy Bitcoin because anyone can create a cryptocurrency is like saying there’s no reason to learn English because anyone can invent a language.
1,041
1,856
208
21,742
1,188,252
Bitcoin Hat Guy🧢 retweeted
INVESTIGATION UPDATE Many of you have asked how personal information ended up in the phishing emails, particularly those who ordered from us years ago. Here is what we have found so far. Phishing emails: We have identified more than 23,000 phishing email attempts across our email systems, including 19,057 messages delivered through Mailgun and 1,503 messages sent through Google Workspace. Some addresses received multiple messages, and some attempts failed or were stopped before delivery. These numbers do not tell us how many people had personal information exposed. We are still determining that number and will share it once we can confirm it. Older orders and abandoned carts (WooCommerce): Before moving to Shopify in May of this year, our store ran on WooCommerce. We had configured automatic redaction of customer details 60 days after shipping. When we viewed those orders in our store admin, the customer details were no longer visible and the orders showed as redacted. During past database migrations, orders were copied into a new set of tables, but copies remained in the old tables. The redaction process updated the newer tables, which were also what our store admin displayed. Orders therefore appeared redacted even though older copies still contained personal information. We also found personal information in other order and refund records, as well as abandoned carts. This included shipping details entered by someone who never completed a purchase. We are still checking the historical settings and redaction process to understand why these records retained data. Those older records were held in systems the attackers were able to reach. We relied on the redaction shown in our admin dashboard, and we now know that was insufficient to verify that the underlying data had been removed. Whatever the shortcomings in the tools we used, protecting your information was still our full responsibility. We plan to share our findings with WooCommerce and the relevant plugin developers. When an order is marked as redacted, its personal information should not remain in another table in the same database. For other WooCommerce store owners: do not rely solely on what your admin dashboard shows when personal data is redacted. Have your developer or agent check the entire database for information left behind, including legacy tables, refund records, and abandoned carts. This is especially important if you have used WooCommerce for years or have been through database migrations. Recent orders (Shopify): Customer details from orders placed on our Shopify store since May may also have been exposed. We are still investigating the extent of any unauthorized access. These orders had not yet been manually redacted. We updated our privacy policy when we moved to Shopify and were building a tool to automate redaction, but automatic deletion was not yet active. Other possible sources: We have received reports of phishing emails containing personal details that customers say they never shared with us. We are investigating whether the attackers combined information from our systems with data obtained elsewhere, but we have not confirmed a connection to breaches at other companies. Historical support records are also part of our investigation. What we have done: We have revoked affected email credentials, cleared queued phishing messages, and taken affected legacy services offline while preserving evidence. Our investigation into the full extent of the compromise is continuing. We have found no evidence that this incident compromised Passport devices or the private keys they hold. The phishing emails are designed to trick you into revealing your recovery phrase, and including your correct personal information makes them more convincing. Never enter your recovery phrase into a website or share it with anyone, including someone claiming to be Foundation. We will continue sharing confirmed findings and publish our full report when the investigation is complete.
37
37
19
168
41,406
Bitcoin Hat Guy🧢 retweeted
ANNOUNCEMENT: SPAM EMAILS HAVE BEEN SENT THAT APPEAR TO HAVE COME FROM OFFICIAL FOUNDATION DOMAINS. We have traced this back to one or more compromised API keys on Cloudflare, and have already revoked all API keys. The malicious domain in the spam email has been taken down. Funds stored on Passport are safe and Passport hardware is not compromised. We are working nonstop to discover exactly what happened and will put out a report ASAP.
101
174
99
508
168,717
Bitcoin Hat Guy🧢 retweeted
New release: Electrum 4.8.3. This release fixes a critical security issue, so we urge all users to upgrade. A description of the vulnerability will be published later today. (note: Windows Defender may show a warning about ZXing.dll, ignore that, it is a false positive)
44
183
76
744
122,594