If #Bitcoin bottoms in October like I believe it will, should I wait until then to share my bullish 2029 price predictions, or should I release them now? π
I've spent this entire time focused on building capital during the Bear Market to maximize gains for the Bull Run.
When the time comes, I'll be just as focused calling the next Bull Run.
One thing I can promise you...
I will nail the next BTC Cycle Top right on target. π―
Mark my words. π₯
@github lmaoooooooo people have been literally BEGGING to help microsoft get their arms around the EASILY DETECTABLE shit in vscode for YEARS now
rip motherfuckers
Fidelity commends the Senate Banking Committee for advancing the CLARITY Act. The bill provides a balanced approach and, if passed, will offer statutory clarity to digital asset markets, benefiting American investors and helping ensure the U.S. remains a global leader in digital assets.
It is time for the U.S. to end military aid to Israel.
But we're not going to wait 10 years to do it.
The time to stop arming Netanyahu and hold him accountable for his crimes against humanity is NOW.
π¨ BREAKING: cPanel and WHM, the control panels behind an estimated 70+ million websites, have a critical security flaw that lets anyone become root admin without a password. CVE-2026-41940 affects every supported version. Itβs already being exploited in the wild.
watchTowr Labs published the full attack today, after the hosting company KnownHost confirmed the bug was already being used to break into a significant chunk of the internet.
If you've never heard of cPanel: it's the dashboard that hosting providers and millions of website owners use to manage their servers, domains, email accounts, databases, and SSL certificates. WHM is the admin version that controls the entire server. If someone gets root access to WHM, they get the keys to the kingdom and to every apartment inside it.
How the attack works, in plain English:
π΄ Step 1: The attacker sends a deliberately wrong login. cPanel still creates a temporary "you tried to log in" record on disk and gives the attacker a cookie tied to it.
π΄ Step 2: The attacker tweaks the cookie to disable cPanel's password encryption. Normally cPanel encrypts the password field on disk. With one small change to the cookie, cPanel just stores it as plain text instead.
π΄ Step 3: The attacker sends a fake login attempt where the password field secretly contains hidden line breaks. cPanel does not strip these line breaks out, so they get written straight to the session file. Each line break creates a brand new fake record. The attacker uses this to inject lines that say "this user is root" and "this user already authenticated successfully."
π΄ Step 4: The attacker visits one more random page on the site to nudge cPanel into re-reading the file. cPanel then promotes the injected fake lines into its main session memory.
π΄ Step 5: On the next request, cPanel sees a flag that says "this user already passed the password check." cPanel trusts that flag, skips checking the actual password, and lets the attacker in as root.
From start to finish, the attack takes a handful of HTTP requests.
If you run cPanel or WHM, the patched versions are:
π΄ cPanel/WHM 110.0.x β 11.110.0.97
π΄ cPanel/WHM 118.0.x β 11.118.0.63
π΄ cPanel/WHM 126.0.x β 11.126.0.54
π΄ cPanel/WHM 132.0.x β 11.132.0.29
π΄ cPanel/WHM 134.0.x β 11.134.0.20
π΄ cPanel/WHM 136.0.x β 11.136.0.5
If your version is older than these, assume someone has already broken in and act accordingly. Patch right now, then rotate every password and key the server touched: root passwords, API tokens, SSL private keys, SSH keys, mail passwords, and database passwords.