LazyNinja (@FreedomIsntSafe) profile picture

Embedded Security Bitcoin click/remove .lol #nostr https://teapawt.net/t.co/ClzZdO0pbU

Bitcoin
Joined February 2016
Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)Photo by LazyNinja (@FreedomIsntSafe)
LazyNinja retweeted
Holy balls the latest update to macOS *ROLLED BACK* the eMudhra cert removal from /etc/ssl/! What the hell are you doing over there, Apple friends?
114
261
59
5,302
390,387
🚨 BREAKING: Hackers are BYPASSING Microsoft 365 MFA, hijacking corporate accounts, and secretly replacing victims' authentication methods to maintain access. 97 accounts compromised across 79 organizations. In some cases, attackers took over sessions in just 12 MINUTES. And now, researchers have separately exposed a critical flaw in Microsoft Authenticator that allowed malicious apps to steal login tokens with ZERO permissions. Microsoft's authentication security is facing two serious threats, and one is already being exploited in the wild. Here's what's happening: 🔴 1. MICROSOFT 365 ACCOUNTS HIJACKED IN THE WILD Cybersecurity researchers at Huntress uncovered a widespread token-replay attack campaign targeting Microsoft 365. The numbers are alarming: → 200,000+ failed login attempts observed. → 497 successful sign-in events. → 97 compromised accounts across 79 organizations. → 48 rogue devices registered inside Microsoft Entra environments. → 19 organizations had victims' MFA methods removed and replaced. Attackers used sophisticated phishing techniques to capture legitimate authentication tokens AFTER victims completed MFA. They then replayed those tokens to access Microsoft 365 without another authentication challenge. But it gets worse. Once inside, attackers registered their OWN authenticator apps and devices to maintain persistent access. They also created hidden email rules to intercept or delete messages involving payroll, banking, and direct deposits. In one case, attackers hijacked a session just 12 MINUTES after the victim reached the MFA prompt and registered their own authenticator less than an hour later. Changing your password alone may NOT remove the attacker. 🔴 2. CRITICAL MICROSOFT AUTHENTICATOR TOKEN THEFT FLAW In a separate discovery, researchers at Enclave exposed CVE-2026-80097 (CVSS 8.6), a vulnerability allowing malicious Android apps to steal Microsoft authentication tokens. → ZERO Android permissions required. → No password required. → No additional MFA prompt. → Malicious apps could impersonate Microsoft Teams. → Stolen tokens could provide access to corporate email, files, calendars, and sensitive account functionality. The underlying flaw? Microsoft Authenticator trusted an application's claimed identity without properly verifying the actual caller. Microsoft has since patched this vulnerability. These are TWO separate security issues, with no confirmed connection between them. But they expose the same dangerous reality: 🚨 MFA ALONE IS NO LONGER ENOUGH TO STOP ATTACKERS WHO CAN STEAL OR REPLAY AUTHENTICATION TOKENS. And businesses relying entirely on MFA for protection may have a serious blind spot. 🛡️ IS YOUR BUSINESS EXPOSED? At Lucid Security, we're offering FREE security reviews to help businesses identify vulnerabilities, authentication weaknesses, and potential security gaps before attackers exploit them. Get your free security review: 🌐 lucidsecurity.si Sources: thehackernews.com/2026/10/mi… enclave.ai/blog/authmask-we-…
🤖 Made with AI
40
303
34
897
116,204
Bill & Keonne are innocent. They did not launder money. They wrote code. The charges were the most convenient legal path to silence brilliant developers. And it still took hiding exculpatory evidence & swapping judges to pull off convictions. #FreeSamourai
3
41
1
123
3,178
THANK YOU TO EVERYONE WHO HELPED GET OUR YOUTUBE CHANNEL REINSTATED. 🧡 BITCOIN IS MORE THAN MONEY. IT’S A MOVEMENT. WE ARE THE CULTURE. 🟠
92
146
8
2,372
29,279
First @SimplyBitcoin and now this. @YouTube this is indefensible.
YouTube has banned The Bitcoin Conference channel. All our channel does is post keynotes and panels from the largest Bitcoin conference in the world, bringing Bitcoin education to the masses. Please reinstate our channel. @YouTube @TeamYouTube
9
7
60
1,392
YouTube has banned The Bitcoin Conference channel. All our channel does is post keynotes and panels from the largest Bitcoin conference in the world, bringing Bitcoin education to the masses. Please reinstate our channel. @YouTube @TeamYouTube
224
312
92
1,588
132,630
LazyNinja retweeted
SATS is now listed on Nasdaq.
 
15.00% fixed annualized dividend rate based on $100 stated amount. Paid every business day.
 
First dividend: November 9, 2026, inclusive of dividends accrued since the October 20 closing.

$SATS $ASST $SATA
107
240
33
1,907
140,312
LazyNinja retweeted
Randy Weaver died in 2022. The shotgun that his wife and son were murdered over is now perfectly legal, and he never got to see it happen.
74
965
40
12,304
197,501
LazyNinja retweeted
🚨SUPPLY CHAIN ATTACK SUSPECTED 🚨 The blast radius could be larger than ledger, It you bought a device through this reseller move your assets immediately.
🚨 CryptoBilis is an authorised resellers of @Ledger yet users got hit hard by either fake or tampered wallet It is also an authorised resellers of: • @Trezor • @coolwallet • @Tangem • @OneKeyHQ • @ELLIPAL • @SafePal Urgent: Are other wallets bought from the same authorised reseller safe to use?
9
20
2
67
6,756
LazyNinja retweeted
Treasury Secretary Scott Bessent: “I am the house now.” The house:
22
43
10
549
17,541
I am working on a second edition of Principles of Economics. If you found any mistakes in the first edition or have any suggestions for improving the book, please email them to me on info @ saifedean dot com
26
25
2
462
25,169
EDWARD SNOWDEN: "People don't realize how hard it is to speak the truth, to a world full of people that don't realize they're living a lie."
34
267
13
1,622
23,477
LazyNinja retweeted
They want a British man named Pip who refers to himself as they/them regulating AI in America. Pound Sand.
502
3,281
202
17,989
256,272
LazyNinja retweeted
I don't give a single fuck about Lindsay Clancy's 'mental health'. You don't think Jeffrey Dahmer & Ted Bundy had mental health issues? WTF is wrong with you retarded bitches?
1,795
11,133
375
87,743
1,137,648
If it was actually important to "pace the frontier", wouldn't the first step be to limit the amount of capital that AI companies can raise? Funny how he doesn't mention that at all. Nobody should trust these guys to influence policy.
We Must Pace the Frontier: I’ve written a new essay on why the AI industry should slow down, with a three-part plan for doing so. Anthropic is unilaterally committing to the first of these steps. We’ll provide third-party evaluators with permanent, employee-level access to our systems, so that they can verify adherence to our safety measures, report on incidents, and assess models’ alignment during training. You can read the full post here: darioamodei.com/post/we-must…
27
100
3
885
55,270
LazyNinja retweeted
Finally able to say that at the end of July, I was involved in the rescue of ~50 BTC which were imminently going to be stolen due to the COLDCARD entropy flaw. The funds are currently held by a Wyoming trust, which will ensure that funds are returned to their rightful owners.
27
22
5
400
63,772
LazyNinja retweeted
Gary Busey looks like shit.
794
1,181
151
21,315
228,044
LazyNinja retweeted
These fucking hags are trying to destroy our country.
This is who the juror had to put up with for 7 days to prevent Lindsay Clancy's acquittal
18
7
246
5,757
LazyNinja retweeted
Liquid hack explained. Liquid has confidential transactions that hide the amounts for improved privacy. A bug in how these transactions are validated caused inflation of Liquid BTC (L-BTC) and allowed hackers to empty the entire side chain. Liquid nodes don't see the amounts of a confidential transaction, so to make sure that the transaction is still valid and doesn't cause inflation nodes check something called a balance proof and a range proof. The balance proof establish that sum of the input amounts equal the output amounts, i.e., that "x L-BTC going in and x L-BTC going out". But there's a catch. Only relying on a balance proof isn't enough. You also need the range proof. The range proof establishes that a hidden output amount falls within a positive range. That means a valid output must be at least 1 L-sat and at most 2^64 − 1 L-sats. Range proofs make sure that you can't mint "negative L-BTC". Why is this even necessary? Remember, the amounts are hidden and a hidden negative amount would allow extra positive outputs to balance against it. Without a range proof, a transaction could say "I've put 1 L-BTC in, and I'm taking two outputs out: one with 4000 L-BTC and one with -3999 L-BTC)." This is going to cause a disaster in a little bit. Once the balance proof, the range proof, and other validations pass, a transaction is regarded as valid and can pass consensus. However, because especially the range proof is computationally expensive, Liquid nodes cache the result of a successful range proof in memory. Essentially, the node remembers "I saw this range proof before and it was valid, all good!". In order to recognize the same range proof later on, you need to assign a label to it. This is called a cache key. This cache key is the actual cause of the bug. The way this cache key was constructed allowed two different transactions to collide on their cache key. Essentially, one valid transaction (1 L-BTC in, 1 L-BTC out) had the same cache key as an invalid transaction (1 L-BTC in, 4000 L-BTC out). Here's the hack: the attackers submitted the valid transaction (1 L-BTC in, 1 L-BTC out) first. Liquid nodes verified this transaction successfully, created a cache key called REKT and stored it in their cache. Then the attackers carefully crafted a second invalid transaction with (1 L-BTC in, 4000 L-BTC out) that created the same cache key REKT. Instead of validating the second transaction and realizing that it printed money out of thin air, Liquid nodes found it in their cache and said "hey I saw this transaction before, everything is fine" and that caused the inflation. The attackers then took their 4000 L-BTC and withdrew 4000 BTC onto the Bitcoin base chain. Note: I might have gotten some details wrong, and I'm aware that I simplified quite a bit. I wrote this post to help people understand what happened. Please feel free to correct me in the comments or add more details below.
82
253
60
1,462
152,344