The security paradigm has significantly changed. Moral panic and influencers won’t protect you. DYOR. infosec will get a LOT worse before it gets better.

🇦🇶
Joined November 2007
Pinned Tweet
Replying to @nvk
BAM! #Bitcoin sent over 7.077Mhz via #JS8Call to @SamuelPatt Sweep: blockchain.com/btc/tx/82c043… Toronto,CAN => Michigan,USA [40W:#SnowStorm] Bcuz its a brainwallet made ahead of time, with bearer pk I don't require internet to broadcast this transaction at the time i'm sending
515
480
259
1,897
NVK retweeted
🚨 MAJOR SECURITY ALERT: bitcoinjs patches multiple high security issues in their packages We hit some of the most critical infrastructure in Bitcoin is dependent on bitcoinjs packages—bitcoinjs-lib, bip39, tiny-secp256k1 were affected are ato multiple high security issues affecting major wallets, protocols, bitcoin infra and sdks : > bitcoinjs-lib: CVE-2026-107846, GHSA-8247-5gp7-95qh, GHSA-4mfv-5394-26c7, GHSA-88jr-9qj4-ccm4, GHSA-h52v-8xwg-7j95 (patch versions: 7.0.5, 6.1.10, 5.2.3) > bip39: CVE-2026-107847, GHSA-39w3-8jr6-f676 (latest patch version: 3.1.12) > tiny-secp256k1: CVE-2026-107853, GHSA-85g9-f6v5-wqq7, GHSA-rm9w-7fv8-3rhx (latest patch version: 2.2.5) All of the above packages have ~500k downloads/week. Also, multiple other CVEs/disclosures took place over more libs of bitcoinjs by other researchers like the ARSB and Bitcoin Red Team: > bitcoinjs-lib: GHSA-4vm8-79jj-j6w4 (patch versions: v7.0.5, 6.1.10, 5.2.3) > bip38: GHSA-mj7w-64jg-8f98 > bip32-utils: GHSA-wvw7-chj5-hr2g(patch version: 0.11.2) > merkle-lib: GHSA-g353-54jg-j6gg (patch version: 2.0.11) > bolt11: CVE-2026-107855 (patch version: 1.4.2) There are a total of 15 findings (14 highs, 1 medium) and cover areas including transaction and block parsing, PSBT fee calculations, proof verification, mnemonic handling and elliptic-curve operations. Their impact depends on the affected version and how an application uses the library. Each advisory explains those conditions and the required remediation. It was greating coordinating with @junderwood4649, @landabaso.
3
11
6
23
2,734
Doing some digging into @FoundationHQ before and after their rebranding into the Bitcoin space that confirms my suspicions and belief through my experiences. Wish I would have done this before. VERY interesting stuff 🫠
3
2
4
708
NVK retweeted
Coinkite’s standard data-retention practice is to blank customer records after 120 days, retaining only email and country. Customers can request earlier blanking after delivery. Our August notice explains the current legal-preservation exception: blog.coinkite.com/update-on-…
1
1
713
FOUNDATION REVEALS HOW CUSTOMER DATA SURVIVED DELETION AND FUELED MASS PHISHING CAMPAIGN Foundation Devices says attackers exploited access to historical customer records that the company believed had been deleted, helping fuel more than 23,000 phishing email attempts targeting its hardware wallet customers. The company discovered that its former WooCommerce store had retained personal information in legacy database tables, even though its admin dashboard showed customer orders as redacted. During previous database migrations, customer records were copied into new tables, but older copies remained. The company's automatic deletion process only removed information from the newer tables, leaving names, shipping details, refund records and even abandoned checkout information accessible. Foundation also confirmed that customer information from recent Shopify orders may have been exposed, as automatic data deletion had not yet been implemented. Investigators identified 19,057 phishing messages delivered through Mailgun and another 1,503 sent through Google Workspace. The total number of affected customers remains unknown. The attackers used authentic personal details to make fraudulent emails more convincing and trick customers into revealing their Bitcoin wallet recovery phrases. Foundation says it has found no evidence that Passport hardware wallets or their private keys were compromised. The investigation remains ongoing.
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.
7
9
1
51
9,556
New ATH in next 6 months confirmed. Classic dumb take we get every cycle.
A brutal year for Bitcoin is just getting started. Give me three minutes to explain why you should dump it now. Outflows from ETFs are signal and will continue. We will test the 57k low again in the next 12 months. Why? Because there are far too many dynamic places to put your money that are creating MUCH more value. Why put your resources into a dead network that offers nothing beyond a store of value? What's the point of place the BTC be if Bitcoin's Ponzi-scheme nature has gone away!?! The viral nature of bitcoin was it's power... if you didn't own you were MOCKED! Now? Completely reasonable, heck, SMARTER, to ignore bitcoin and place other bets! No one is trying to convince people to buy Bitcoin anymore... the memes and NFTs are gone. No one is saying $ BTC can change the world, because it won't — and BECAUSE AI HAS! Just sell and shift from Bitcoin to Super Intelligence because one provides little to no value, and the other provides unlimited upside for humanity. This should be obvious to everyone right now. Bitcoin will never break its all-time high again.
6
3
45
4,180
NVK retweeted
📱 Motorola ouvre une porte de sortie GrapheneOS va ENFIN tourner sur un téléphone qui n'est pas un Pixel - Pas de Google au cœur du système - Motorola fournit lui-même les pilotes et le firmware au projet - Et à terme, le Signature 27 sera vendu avec @GrapheneOS préinstallé On en a parlé quelques fois ici... jusqu'à maintenant pour se dégoogliser il fallait acheter un téléphone... Google ! Ce paradoxe est en train de tomber Le support n'est pas disponible avant 2027, le portage est en cours. Pour l'instant le téléphone sort sous l'Android de Motorola Bref... Pendant que d'autres veulent filtrer le réseau... Vous, vous pouvez reprendre le téléphone 😉
Elegantly crafted. Seamlessly contoured. Thoughtfully detailed. motorola signature 27 is designed to a higher standard. #MotorolaSignature #SignatureStatement
37
164
13
1,091
29,905
I joked about CatCard being the “ColdCard x Mt Gox collab” but after spending weeks going down a self custody research rabbit hole I like this more and more especially as part of a multi-vendor/sig setup. @MagicalTux isn’t getting enough credit for this one, but it’s pretty impressive.
5
20
2,292
🚨FLAVIO BOLSONARO LOGRÓ ESCAPAR DE LA DICTADURA DE LULA DA SILVA Cruzó la frontera hacia Misiones y de ahí se tomó un vuelo privado a Estados Unidos. En Brasil se terminó la democracia.
1,125
7,434
384
42,988
1,328,165
Multi-vendor multi-sig users today having combined each of these gems into a 3-of-5
"the password you are attempting to use was part of a data breach are you sure you want to continue using it?" drone strike my house man i don't care anymore
8
2
1
28
3,630
‼️ UPDATE - Tailscale confirms the Tailworm SSH flaws are real. Its new investigation page says most of what it found is privilege escalation and calls the issues “serious.” Fix targeted within 24 hours — no CVE or patched version out yet. Mitigate now: → Set TS_SSH_DISABLE_FORWARDING=1 in the tailscaled service and restart → Tighten SSH access rules to the users/devices that need them Read: thehackernews.com/2026/10/un…
46
175
46
969
127,505
💥EXPLOSIVE ATIP: Immigration Canada knew Indian agents were running MASSIVE FRAUD in the trucking industry and the student visa program as early as 2017 — and stamped the evidence "DO NOT DISCLOSE." According to records released under the Access to Information Act, Immigration, Refugees and Citizenship Canada (IRCC) maintained an internal procedures manual for its New Delhi visa office documenting systemic fraud across the student visa and temporary foreign worker streams. The manual instructs officers to treat fraud as anticipated rather than exceptional The most damning thing about this scandal is not the fraud — it's that the government predicted it, kept it running, and then stamped the file "DO NOT DISCLOSE." Canada didn't lose control of its immigration system—they monetized it.
319
3,166
310
7,111
225,991
Announcing 3 Critical vulns for hundreds of millions of IoT, Firewalls, OT, and Military devices including: Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin, Boeing... The vulns are with GoAhead Web Server which is a backend library used by these devices. There's a patch available from GoAhead but that doesn't mean there's a patch available for the devices yet -- that's up to the manufacturer. - TLS traffic over DHE ciphers have a 1-byte secret, "04", meaning anyone can decrypt connections to these devices and steal login credentials and session tokens if the client negotiated with DHE ciphers like the latest TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, which is extremely likely. - LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS. If you have one of these devices listening on the internet and are expecting mTLS to protect it from attackers, take it offline or patch asap. - OpenSSL Certificate Revocation Lists (CRLs) are not enforced, meaning if a user device is stolen or compromised, and you revoke that mTLS cert, nothing actually happens. There are a lot of other attacks this can be used for. These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure. foxio.io/blog/choose-your-ba…
59
269
147
1,509
276,841
🚨 New release 2.8.5 is here ❗ Security updates 🔧 Improved coinjoin stability 🌙 Payjoin (BIP78) discontinued
3
9
1
34
3,393
NVK retweeted
Apple dropped Private Cloud Compute source for researchers. github.com/apple/security-pc… CloudAttestation. Thimble / privatecloudcomputed. CloudBoard. log filters. srd_tools VRE. the pieces that claim device-class trust for Apple Intelligence in the cloud. this is not a marketing PDF. it is a hunt surface. revocation already bit them once in CloudAttestation X509Policy. fixed in 26.4. Apple Security Bounty covers PCC guarantee breaks. guide: security.apple.com/documenta… #iOS #AIRedTeam #InfoSec
3
36
1
201
18,089
“Security is like Tetris: Your successes disappear but your failures pile up.” — Mikko Hyppönen
5
109
4
658
25,569
I heard OpenAI are testing GPT-7 Astra inside vim so the agents can’t escape.
61
168
21
2,620
75,203
NVK was right about HWW genuineness theater and the need to physically examine the PCB through a clear case. Nobody wants to hear it but it needed to be said.
WHAT?!!!!!!!!!!!!!!!!!! 🤬
3
1
12
2,436
Well, I am no Nostradamus but I warned 9/4/26 @FoundationHQ ; too bad this wasn’t done or even responded to 🤔 Shopify…. Known risk vector Got the email as a recent customer, so can confirm Opsec identity once lost cannot be regained. @zherbert
Since @FoundationHQ uses Shopify, has the company thought about a way to get them to delete Foundation purchase history from user accounts once shipped? The same exposure could happen to Foundation users if Shopify was hacked.
1
1
5
2,041