kfx (@crypto_kfx) header
kfx (@crypto_kfx) profile picture

Got bored. Privacy | Security | Social Engineering stuff. Contributing to @BoringSecDao. May share other boring things. #BAYC 4522

#VegasApes
Joined January 2018
Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)Photo by kfx (@crypto_kfx)
Nothing, then all at once.
1
5
326
kfx retweeted
Ledger decided to factory reset itself and I won't be able to piece together my seed for another ~10 days. Got caught with not enough redundancy, lesson learned. Effectively locked out of most of my wallets for now.
94
12
9
395
174,799
I really recommending reading this. In summary, a company which does ID verification for in-person interactions (hotels, car rentals, ID verification for alcohol or marijuana, etc) has some how exposed over 153,000,000 drivers licenses for people in the United States and Canada. It is a catastrophic data breach, probably one of the worse I've ever seen. If you're in the United States and have traveled, gotten a hotel, purchased marijuana or alcohol, there is a high probability you're in this. Unlike other breaches, this includes a photo of the person (from the license), making verification you've identified the person significantly easier. This poses a significant threat to celebrities (musicians, YouTubers, streamers, adult entertainers, actors, etc), politicians, lawyers, wealthy people (CEOs, investors, people of public interest), Law Enforcement Officers, etc Krebs himself, and several other security researchers, have already confirmed they're in the data leak. tl;dr gah damn dawg this company is going to be sued into oblivion krebsonsecurity.com/2026/09/…
387
3,298
668
19,210
4,842,045
📱GrapheneOS sort enfin de la prison Pixel ! Pendant des années, le message était clair : Tu veux un téléphone vraiment privé ? Tu prends un Pixel. Point final L’OS le plus sérieux en matière de confidentialité, n’acceptait que les Google Pixel Pas par snobisme mais par exigence Il exige des fonctionnalités matérielles que presque personne n’avait : - Un Secure Element capable d’appliquer un vrai rate-limiting (20 tentatives max, délais qui montent jusqu’à 41 jours) - Une résistance aux attaques "insider" (même un fabricant sous pression ne peut pas facilement retirer les protections) - Le Hardware Memory Tagging (MTE) pour rendre les exploits mémoire beaucoup plus difficiles - Une intégration propre avec le reste de la stack de sécurité Les Pixel (depuis le Pixel 2) avaient ça grâce au Titan M La plupart des Snapdragon, MediaTek et autres puces étaient trop en retard Résultat : monopole de fait Tu voulais te protéger de Google... tu devais quand même lui acheter ton téléphone 🙄 En mars 2026, Motorola (Lenovo) a annoncé un partenariat à long terme avec GrapheneOS Grâce aux avancées de Qualcomm, les prochaines générations de Snapdragon intègrent enfin nativement le Memory Tagging et les fonctionnalités de Secure Element que GrapheneOS exige Les futurs flagships Motorola (Signature, Razr Ultra, Razr Fold et leurs successeurs) devraient être les premiers appareils hors Pixel à être officiellement supportés C’est du matériel conçu (ou au moins validé) pour répondre aux standards de GrapheneOS. - On sort enfin de l’exclusivité Pixel - On a une alternative hardware - On n’est plus obligé de financer Google pour se protéger de Google !! Bref... Le vrai sujet n’est pas #Motorola vs #Pixel Le vrai sujet, c’est qu’on en est encore à se réjouir qu’un constructeur accepte enfin de produire un téléphone suffisamment sécurisé pour qu’on puisse y installer un OS libre et durci 🫠 Dans un monde normal, ce serait le minimum Dans le nôtre, c’est devenu un événement !! Parce que se protéger est devenu suspect Parce que vouloir un téléphone qui ne te surveille pas en permanence est devenu "extrême" ?? Parce que les outils open-source qui marchent vraiment sont de plus en plus regardés de travers ! @GrapheneOS n’est pas une solution magique. C’est juste l’un des rares projets qui refuse encore de baisser le niveau de sécurité pour plaire au marché Et le simple fait qu’un grand constructeur accepte de travailler avec eux, et que Qualcomm fournisse enfin le matériel nécessaire, est une bonne nouvelle Petite Lente Mais réelle On avance Pas assez vite Mais on avance 🙏 #Privacy
GrapheneOS has strong defenses against data extraction. It heavily builds upon the standard security features provided by Android 17 and the most secure hardware available for Android. Currently, only Pixels provide the hardware security features and updates required by GrapheneOS. That's going to change in 2027 thanks to our partnership with Motorola Mobility and progress being made by Qualcomm. Disk encryption provides strong protection for data. Even the most sophisticated attackers aren't going to be directly breaking it. They either need to exploit the OS while in After First Unlock state or brute force the PIN/password. Android 16 QPR2 calls for a secure element implementing rate limiting ramping up delays. It's 4 hours after 10 and 41 days after 15. Only 20 attempts are allowed. For usability, It rejects the most recent 5 unique failed attempts early to avoid wasting attempts on repeated errors. GrapheneOS only supports devices implementing the latest generation secure element rate limiting. source.android.com/docs/secu… The secure element on the supported devices also has insider attack resistance. That's implemented by requiring the Owner user to successfully authenticate before the secure element firmware can be updated. A valid signing key and greater version number aren't enough alone. The purpose of this is preventing any government from bypassing the rate limiting by coercing the creation of a firmware update removing the rate limit. Pixels have used a secure element with an internal timer implementing rate limiting and insider attack resistance since the Pixel 2 launched near the end of 2017. Here's a post about this from back in 2018: android-developers.googleblo… The secure element and integration into the OS has become far better since then, but it shows this goes back a long way and isn't a new feature. GrapheneOS also raises the character limit for passwords from 16 to 128. This enables using high entropy diceware passphrases not depending on the secure element rate limiting. To make a strong passphrase convenient to use without ruining it with biometric unlock, GrapheneOS adds an optional 2nd factor fingerprint PIN. We reduce the allowed fingerprint attempts from 20 to 5 and failure to enter the correct 2nd factor PIN counts towards it. This enables using 6-8 random diceware words as the main unlock method required in Before First Unlock and fingerprint+PIN using a short PIN for convenience. Using a valid fingerprint prompts to enter the 2nd factor PIN which is needed to complete unlocking the screen and hardware keystore. GrapheneOS greatly improves the exploit protections for the OS with hardened memory allocators and other features. It heavily uses hardware-based security features including hardware memory tagging (MTE) to protect against exploits. A partial overview of those protections is here: grapheneos.org/features#expl… GrapheneOS adds specialized protection against attacks with physical access too. For example, it blocks new USB connections at a software and hardware level by default while locked and disables USB data as soon as there are no active USB connections. GrapheneOS shipped a locked device auto-reboot timer back in June 2021. It can be set between 10 minutes and 72 hours. We enabled it by default using 72 hours and then lowered it 18 hours. It automatically returns the device to Before First Unlock state due to our memory zeroing as part of tearing down the OS and booting. We got Pixels to add memory zeroing for booting the firmware fastboot mode in April 2024. Apple and Google added a locked device auto-reboot timer in iOS 18.1 and Android 16. For Android, it can be enabled with the Android Advanced Protection Mode. Our implementation is better for multiple reasons but it's a useful feature regardless. Android uses separate encryption keys for each secondary user and Private Space. GrapheneOS adds support for putting both back into Before First Unlock state without a reboot via end session for secondary users or toggles for either to do it by default. It's still much better for the device to be rebooted to get the main user back at rest, completely clear leftover data from RAM and block secure element updates. Our duress PIN/password feature is a minor feature fitting into the bigger picture. It wipes the device when it's entered in any OS prompt for the current profile's PIN or password. It will wipe the device when entered into the authentication prompt for changing a sensitive setting or anything else requiring it, not only the lockscreen. It works across every profile including secondary users and Private Spaces, not only the main user. There are multiple ways to use the duress PIN/password feature including writing it down on a phone case or a paper kept in a wallet. People should carefully consider how to use it in an actual duress situation where there can be physical or legal consequences for wiping the device. GrapheneOS doesn't require it to protect data from being extracted from the device, but it takes recovering it completely off the table even with the PIN/password for each profile on the device. GrapheneOS doesn't depend on the duress PIN/password to protect user data. It's one of the tools it provides among the major privacy and security improvements it offers as a whole. Our features page provides an overview of what GrapheneOS offers compared to standard Android 17. It covers most of the major features we provide and many of the minor ones but there's also a lot more beyond it. Our release notes are a lot more exhaustive since we make sure to cover everything when it's added, changed or removed. grapheneos.org/features grapheneos.org/releases#chan…
81
725
33
4,312
220,057
Proton VPN just shared that it received 47 legal orders through June this year, all seeking to identify users behind specific server IPs and timestamps. Every one was denied, because its no-logs policy leaves no connection data to hand over. Per its transparency report, updated July 14, that brings the total since 2019 to 458 orders, with zero fulfilled. The company keeps no connection logs under Swiss law, so there is nothing to produce even when an order is binding.
128
912
64
6,955
286,496
kfx retweeted
I don't care how many signers your multisig has, if all of the private keys exist on a single internet connected device then it's a hot wallet. Humanity secured a billion dollar protocol with a hot wallet.
25
14
5
162
16,380
"Age verification lays the foundation for a fully government controlled internet." — @mullvadnet with an amazing takedown "If age verification is introduced, everyone will have to identify themselves either to the service/website they want to use or to a third party capable of linking them to their activity on that service/website. The correct term for age verification as it is implemented today is therefore identity verification."
24
442
13
971
40,061
Where is your seed phrase stored right now? No, seriously. Because if it's stored in ANY of these places, malware can find it in seconds: ❌ Notes app ❌ Photos ❌ Email ❌ Google Docs ❌ iCloud backups ❌ Encrypted USBs ❌ Anywhere online Most people think: "It's encrypted, so I'm safe." Wrong. Modern wallet-stealing malware doesn't care where you hid it. It searches your device for 12- or 24-word combinations matching the 2,048 simple words your seed phrase is generated from and sends them to the attacker automatically. Your wallet can be emptied before you even realize you're infected. And here's the uncomfortable truth: If you created your wallet in a browser or on your phone, that seed phrase was generated online... So what should you do? ✅ Buy a hardware wallet ✅ Generate a new seed phrase ✅ Store the seed phrase offline Best options: • Paper backup stored securely (Minimum) • Metal backup (CryptoTag Zeus, etc.) (Preferred/Recommended) If you need help my DMs are always open! Stay Safe & Stay Vigilant
7
6
3
33
2,189
kfx retweeted
Everyone in Web3 should take the Boring Security course with Dreww and KFX 🔐✨ They give excellent reminders and advice that everyone should know. ————————- @BoringSecurity @nft_dreww @crypto_kfx
2
2
13
260
Okay I think I’m back..
19
26
179
We need more open source privacy software in crypto, so I minted one of the @rotkiapp supporter NFTs tonight. Cool product well worth supporting, but it's even more important to use tools like this to keep your privacy!
Replying to @ethereum
21/ Many privacy projects from @rotkiapp to @fileverse often struggle to keep the lights on. That’s a crazy situation and we shouldn’t stand for it. Contribute to privacy projects with your wallet. Recently, over 100 projects participated in public goods pro-privacy rounds on Gitcoin and Octant:
1
2
15
1,802
Get a damn audit... Smart Contract Audit: $50K+ Security Audit on Socials/Discord: $5K+ Security Training/Consulting: $5K+ Total Audit Costs: $60K+ Exploit Cost: $2.2 Million.. % of Business that don't recover after an exploit: 83% Be smart, get an audit! DM me for more info!
6
7
37
1,620
Magic Eden Shutting Down Support: What does this mean for you? With @MagicEden shutting down support for all NFTs except SOL and discontinuing their wallet, there are steps EVERYONE should take ASAP, Let’s review them below ⤵️ 1/ EVM Marketplace and Approvals 2/ Magic Eden Wallet 3/ Stay Safe from Scams
12
21
5
75
23,923
Absolute cinema
The Crypto Kidnapping
3
10
182
Sigh
Ubuntu Planning Mandatory Age Verification Ubuntu & Elementary OS developers are planning to add age verification functionality, in a way which impacts all Linux users, to comply with a new California law.
1
5
133
🦔 Security researchers discovered the first Android malware that uses AI to help it survive on your phone. The malware, called PromptSpy, sends Google's Gemini model a screenshot of your screen and asks it how to lock itself into your recent apps so Android won't kill it. It loops through this until Gemini confirms success. Beyond the AI trick, it's full-featured spyware. Remote access, intercepting your lockscreen PIN, recording your unlock pattern as video, capturing screenshots, and tracking what apps you're using. To block removal, it overlays invisible buttons over "uninstall" so tapping them does nothing. My Take This is where malware is headed. Traditional malware relies on hardcoded scripts that break when devices differ. Using an AI to look at the screen and figure out what to do next makes malware adaptable in ways that used to require much more sophisticated programming. The AI isn't writing the malicious code, it's just helping the malware navigate your phone, but that's enough to make it way more reliable across different devices. I don't think Google is liable here since Gemini has no idea it's helping malware. But as AI gets embedded into more attack chains, these companies will face pressure to detect and block malicious patterns. Whether that's possible without breaking legitimate uses is an open question. For now, be careful what you install, and if an app asks for Accessibility permissions and you don't know exactly why it needs them, don't grant it. Hedgie🤗
68
711
94
3,158
173,515
A man posing as a postal worker attacked a man and his wife in broad daylight last Friday in Seattle, Washington. He handed the homeowner a letter demanding cryptocurrency before forcing his way in to the home. Police arrived to find the suspect and homeowner fighting inside. After detaining the suspect, they searched his postal bag finding tape, plastic bags, zip ties, tasers, an electronic signal blocking pouch, a black beanie, face mask, and plastic gloves. The attack is a strong reminder that criminals will disguise themselves as legitimate personnel (delivery drivers, postal workers, or even police) to manufacture a reason to enter the home. Good job by the victims for fighting back and getting the attention of police
15
4
55
2,778
This is a 10-15 min read on the security things you should prepare for in bear markets. Don’t let prices going down be the least of your problems, take care of your security!
9
12
2
61
7,850
OPSEC folks. Remember it
This Post is from an account that no longer exists. Learn more
3
5
142
Do you use a Ring Camera? If so, consider disabling this setting asap ⤵️ Ring's Super Bowl commercial showcased a new feature called "Search Party" that lets you use your neighbor's Ring camera to find a lost puppy. While this sounds helpful in theory, it's a major privacy violation imo, Amazon just created the largest surveillance network without deploying any hardware themselves... Currently, this feature is used for finding lost pets and monitoring fire hazards. But companies that collect data always start with a practical use case before expanding far beyond it. What's worse: This feature is enabled by default, forcing you to opt out instead of opting in. To opt out of the Ring Search Party feature (enabled by default for users with cloud storage): Open the Ring app, tap the three-line menu, go to Control Center > Search Party, and toggle off "Search for Lost Pets" and "Natural Hazards" for your cameras. I hope we don't see more of this from Amazon and other surveillance companies, but I suspect we will. Stay Safe & Stay Vigilant
12
6
25
1,914