#Bitcoin | Slivers of truth that cut like razor blades | Miner | Featured In the WSJ, Forbes, & Barstool Sports
USA
Joined December 2017
- Tweets86.4K
- Following2.4K
- Followers12.2K
- Likes86.6K
MeanHash ₿ ✪ retweeted
Let me get this straight.
A guy keeps getting weirdly targeted ads on his new Samsung TV.
So he breaks into his own TV to find out why. 1.2M people watch.
42 hours later, OpenAI deactivates his account. Reason: "Cyber Abuse."
His words: "i have never used openai to exploit or find vulnerabilities, only local reverse engineering"
Same week, people on r/claude say Claude now cuts off reverse-engineering write-ups MID-SENTENCE:
"A safety check stopped my response partway through creating the playbook"
The TV is fine.
The guy who opened it is the problem.
banned for reverse engineering work? that’s wild
oh well, -$500, and a bunch of banked resets) but gained motivation to get 3 more machines and finish my cluster.
i have never used openai to exploit or find vulnerabilities, only local reverse engineering which tripped daybreak.
Exploits EVERYWHERE
ELECTRUM BITCOIN WALLET CONFIRMS CRITICAL SECURITY VULNERABILITY EXPLOITED IN THE WILD
Electrum has disclosed a high-severity vulnerability allowing malicious servers to trick users into sending Bitcoin to an attacker when increasing a transaction fee.
The attack works by intercepting a broadcast transaction and replacing it in the wallet’s history with a fake transaction redirecting funds to an attacker-controlled address.
If the user attempts to increase the fee using Replace-by-Fee (RBF), Electrum can sign the malicious transaction, sending the Bitcoin to the attacker.
Electrum confirmed two reported incidents, including one user who lost funds. Attackers even generated addresses matching the last four characters of the intended recipient’s address.
The vulnerability affects versions before 4.8.3 and has been patched in the latest release.
Users are urged to update immediately and verify all destination addresses and amounts before signing transactions.
MeanHash ₿ ✪ retweeted
I'm actually okay with France and most of Europe being a new experiment in why communism doesn't work.
People in North America clearly need the lesson ASAP.
MeanHash ₿ ✪ retweeted
the cloudflare CEO just said something that should make every developer on the internet uncomfortable
cloudflare’s CEO just announced they’re expecting another critical vulnerability disclosure on par with the PHP flaw that broke the internet last week. not speculation, he said it’s “almost certain”
and it gets worse. he says they already have prior information about flaws in other software that haven’t been disclosed yet. multiple disclosures coming in the next few weeks to months
polymarket already opened a betting market on whether another major PHP flaw gets disclosed. that’s where we are right now. people are literally gambling on the next vulnerability
this is not normal. a CEO of one of the biggest infrastructure companies on the internet doesn’t come out and say “more is coming” unless he knows something specific. cloudflare sits between users and websites, they see everything before anyone else does
if you haven’t rotated your keys, updated your dependencies and enabled 2FA on everything by now, i genuinely don’t know what you’re waiting for
black october has a sequel and we’re watching the trailer
MeanHash ₿ ✪ retweeted
I hate Michigan as much as the next Buckeye fan, but that might be the WORST roughing the passer call I’ve ever seen.
Am I crazy, or was that an absolutely HORRIBLE call? 👀
Yeah, at this point I do not think anything that touches the internet is safe.
Going fishing, not answering emails or calls this weekend, will pray the internet is still on by Monday.
⚠️🚨 THIS IS NOT A DRILL 🚨⚠️
Google has officially declared a bug in Brotli, its tool that shrinks web traffic, CRITICAL: 9.2 out of 10. Last night "Node2Shell" evolved into HTTP2SHELL.
A formal CVE record has been issued citing CVE-2026-111497 -- a hole in versions 1.0.3 to 1.2.0 that can hit any app unpacking data from strangers, and could let them take it over.
What this means:
▪️ This is not a Node.js problem anymore. This is an HTTP PROBLEM.
▪️ Every unpatched app across Node.js, Python, Bun, and Envoy that unpacks Brotli now has a hole attackers need no login to use
▪️ Istio. curl. Python's requests and httpx. All at risk under one CVE.
▪️ EVERY project that bundles Brotli must ship its own fix, and not all are out yet
This changes everything.
A normal bug can be fixed in one place.
A 9.2 bug inside a shared tool cannot.
We just entered the most dangerous phase of this crisis. If you're not paying attention - start now.
Save this. Share this. This is the moment it escalated beyond return.
No, most people have absolutely ZERO idea about how fucking insane that is...
MeanHash ₿ ✪ retweeted
We had a Linux server that showed two successful SSH logins from an external IP overnight.
The strange part was that there were no failed password attempts before them.
The attacker got in cleanly.
So I checked the SSH logs properly.
Both sessions said:
Accepted publickey
That meant we were not dealing with a guessed password.
I pulled the fingerprint from the logs and compared it with the keys in:
/home/deploy/.ssh/authorized_keys
There was only one key there.
And it matched.
The comment on the key was:
deploy@old-build
That name sounded familiar, so we checked our records.
The build server it belonged to had been retired months ago.
But nobody had removed its SSH key from this production server.
I checked the timestamp on authorized_keys.
The key had been sitting there since November 2025.
So this was not some new persistence the attacker had just created.
It was an old trust relationship we had forgotten about.
That was actually worse in a different way.
I checked the login history and confirmed both sessions came from the same external IP.
Then I looked for files touched during those sessions.
A backup copy of the application’s .env file had been created under /opt/api/.
That immediately raised another concern because environment files often contain things like database credentials, API keys and application secrets.
At that point we disabled the deployment account, removed the stale key, rotated the application secrets and started checking every other server that might still trust the same old build key.
The lesson from this one was simple.
Not every compromise starts with malware.
Sometimes the attacker just finds a credential or key that your own environment forgot existed.
Passwords expire.
Employees leave.
Servers get retired.
But SSH keys can quietly sit in authorized_keys for years if nobody is actually reviewing them.
That is why key rotation and access reviews matter.
The attacker did not need to break SSH.
We had already left the door open.
MeanHash ₿ ✪ retweeted
🚨 BOOM! EPSTEIN'S ZORRO RANCH HORROR UNEARTHED — THEY'RE DIGGING FOR BURIED BODIES RIGHT NOW AS SHOCKED VICTIMS EXPOSE BEING DRUGGED, HARVESTED FOR SEX ORGANS & SPERM, AND WAKING UP TO MYSTERIOUS MEDICAL EQUIPMENT IN A LIVING NIGHTMARE!
The Deep State elite's twisted eugenics lab is finally cracking wide open — these monsters treated humans like livestock for their sick experiments!
TIME TO REVISIT THE MONDAY EVENT.
MeanHash ₿ ✪ retweeted
There is nothing to worry about.
Nothing important is run on PHP or old software—except the water & electrical grid, a few government services like our missile defense systems and a handful of electrified fences at the zoo (for the lions, tigers and cobras).
MeanHash ₿ ✪ retweeted
PSA
It is VERY ILLEGAL to alter this mans picture in the UK
Whatever you do, please DO NOT alter or satirize this picture in any way.
The UK police would REALLY not like that.
MeanHash ₿ ✪ retweeted
Claude Code found every photo i "permanently deleted" from my iPhone. 3 years of deleted photos and videos sitting in a hidden cache on my device that any app with file access can read.
i plugged my iPhone into my MacBook to run a backup. had Claude Code doing the security audit from my last post. it flagged something i wasn't even looking for. a directory called PhotoData/Thumbnails with over 147,000 files. photos, videos, screenshots. every single one was something i deleted.
photos from 2023. 2024. 2025. photos i deleted the second after taking them. photos i went into Recently Deleted and manually hit Delete All on. photos i deleted three separate times because i wanted to be absolutely sure they were gone. all still there.
what was sitting in that cache:
a photo of my passport i took for a visa application in 2023
screenshots of my bank app with full account numbers visible
private photos i sent someone and immediately deleted after a breakup
a screenshot of my crypto seed phrase i took "temporarily" in 2022
a photo of my ID and credit card i took to remember the numbers and deleted 5 seconds later
screenshots of my ex's private instagram stories i saved and "permanently deleted" in 2023
147,863 files in total. some of them were full resolution and all of them were organized by date going back to 2021.
when you delete a photo on iPhone, iOS removes it from your camera roll and your Recently Deleted folder. but it keeps a compressed copy in a Spotlight search index cache. this is how your phone finds photos when you type a word in search. Apple never clears it. not after 30 days. not after a year. not ever. they told you it was permanently deleted. it wasn't.
i checked which apps on my phone had Files and Folders access. 23 apps. weather apps. QR code scanners. PDF readers. a flashlight app i downloaded in 2022. any one of them could have been reading every photo i ever "deleted" this entire time.
went from 23 apps to 3 in about two minutes.
the full step by step is below. takes 2 minutes. save it so you don't lose it and send it to anyone with an iPhone.
MeanHash ₿ ✪ retweeted
ASUS is releasing urgent updates for some of its Wi-Fi 7 routers after serious security flaws were discovered.
The vulnerabilities could allow hackers to gain control of an affected router and run their own commands.
One of the flaws is rated 9.4/10, or Critical, because it can potentially be exploited using a specially created VPN configuration file.
ASUS has released fixes for affected models, including the RT-BE88U and RT-BE92U.
If you have an ASUS Wi-Fi 7 router, check for a firmware update and install the latest version for your model.
