Personally a poet. πͺ·
Georgia, USA
Joined December 2022
- Tweets16.2K
- Following686
- Followers720
- Likes55K
Raising money for her ring the only way I know how: by finally publishing the thriller I've been plotting for years. New chapters weekly. Read the Prelude and first one free π
Expect a flurry of such frivolous lawsuits.
BREAKING: The Trump administration sues to block Alaska Senate certification if Republican Sen. Dan Sullivan loses as another candidate shares his name. apnews.com/article/alaska-seβ¦
eMudhra and PHP2Shell vulnerabilities were deliberate intelligence architecture rather than incompetence, you look through the lens of modern SIGINT doctrine: plausibly deniable "bugdoors" and supply chain capture.
Hardcoded backdoors get caught; architectural memory flaws and botched cryptographic scripts provide total deniability under Hanlon's Razor. Together, compromising a global Certificate Authority (data-in-transit + OS code-signing) and the core PHP engine (execution layer on roughly 75% of the web) gives an intelligence coalition full-spectrum access.
There is a real effort to limit your AI usage to government approved models. Add that to your cogsec
Since everything is getting hacked let me say I'm not ashamed of what you might find.
I should be, but I'm not.
SITUATION DETECTED: #3 tech poster just greenlit slopcannon
Notice how these things keep leaking before they post the security patches. I think this is a coordinated thing.
Smells like inventing a problem to sell the cure
π¨ BREAKING: LINUX IS NOW FACING TWO CRITICAL SECURITY VULNERABILITIES, AND THERE ARE NO OFFICIAL KERNEL FIXES YET.
Both rated 9.0/10 in severity.
One could allow hackers to take control of vulnerable servers WITHOUT EVEN LOGGING IN.
And the most alarming part? The flaws were made PUBLIC before patches were ready.
Here's what's happening:
β TWO CRITICAL RCE FLAWS: Both affect KSMBD, Linux's built-in SMB file server.
β NO PASSWORD REQUIRED: One vulnerability could allow unauthenticated attackers to execute malicious code on vulnerable servers.
β KERNEL-LEVEL ACCESS: Successful exploitation could potentially give attackers control within the Linux kernel itself.
β NO MAINLINE PATCH YET: Both vulnerabilities were publicly disclosed before official kernel fixes were available.
β DISCOVERED BY AI: Trend Micro's AI-powered security scanner identified the flaws.
β SERVERS AT RISK: Linux systems running the vulnerable KSMBD service need immediate attention, especially if port 445 is exposed.
First PHP. Then Node.js. Then GitLab. Then Python.
NOW LINUX.
And this time, the vulnerabilities are PUBLIC before the fixes are ready.
If you manage Linux servers, CHECK YOUR EXPOSURE NOW.
Readers added context they thought people might want to know
KSMBD is a rarely used optional in-kernel SMB server distinct from the common Samba implementation; it is not enabled or shipped by default on major distributions like RHEL, and the flaws affect only systems explicitly running it with port 445 exposed.
thehackernews.com/2026/10/two-cvβ¦
threatlandscape.io/blog/ksmbd-zdiβ¦
π½πΌππππ πππΏππππππΌπ πππππ retweeted
π¨ BREAKING: LINUX IS NOW FACING TWO CRITICAL SECURITY VULNERABILITIES, AND THERE ARE NO OFFICIAL KERNEL FIXES YET.
Both rated 9.0/10 in severity.
One could allow hackers to take control of vulnerable servers WITHOUT EVEN LOGGING IN.
And the most alarming part? The flaws were made PUBLIC before patches were ready.
Here's what's happening:
β TWO CRITICAL RCE FLAWS: Both affect KSMBD, Linux's built-in SMB file server.
β NO PASSWORD REQUIRED: One vulnerability could allow unauthenticated attackers to execute malicious code on vulnerable servers.
β KERNEL-LEVEL ACCESS: Successful exploitation could potentially give attackers control within the Linux kernel itself.
β NO MAINLINE PATCH YET: Both vulnerabilities were publicly disclosed before official kernel fixes were available.
β DISCOVERED BY AI: Trend Micro's AI-powered security scanner identified the flaws.
β SERVERS AT RISK: Linux systems running the vulnerable KSMBD service need immediate attention, especially if port 445 is exposed.
First PHP. Then Node.js. Then GitLab. Then Python.
NOW LINUX.
And this time, the vulnerabilities are PUBLIC before the fixes are ready.
If you manage Linux servers, CHECK YOUR EXPOSURE NOW.
π¨ BREAKING: IT JUST KEEPS GETTING WORSE. NOW PYTHON IS FACING A MASSIVE SECURITY EMERGENCY.
Python's security team has issued an URGENT warning after a certificate authority compromise put Python's HTTPS security at risk.
β 8 CERTIFICATE AUTHORITY KEYS COMPROMISED. Some were so weak they could be cracked almost INSTANTLY.
β FAKE TRUSTED WEBSITES: Attackers could potentially impersonate Python.org, PyPI and other websites during intercepted connections.
β MALICIOUS DOWNLOADS: Vulnerable environments could be tricked into downloading software from attacker-controlled servers.
β YOUR OS PATCH MAY NOT PROTECT YOU: Older versions of pip can STILL trust compromised certificates even after system updates.
β EMERGENCY UPDATES: Python developers are being told to immediately update pip, certifi, uv and other affected tools.
β DOCKER USERS AT RISK: Existing container images may retain vulnerable certificate stores and need rebuilding.
First PHP. Then Node.js. Then GitLab. Then LiteLLM.
NOW PYTHON.
The very systems developers rely on to establish TRUST online are becoming the attack surface.
If you use Python, PATCH NOW.
Readers added context they thought people might want to know
The Python certifi/pip details match the real eMudhra CA incident, but PHP, GitLab and LiteLLM involved unrelated software bugs, platform flaws and supply chain malwareβnot CA key compromises like this (Node.js patched concurrently for the same CA issue).
discuss.python.org/t/information-β¦
emudhra.we-have-a-problem.com
github.com/advisories/GHSβ¦
docs.litellm.ai/blog/security-β¦
snyk.io/blog/php-patchβ¦
Readers added context they thought people might want to know
KSMBD is a rarely used optional in-kernel SMB server distinct from the common Samba implementation; it is not enabled or shipped by default on major distributions like RHEL, and the flaws affect only systems explicitly running it with port 445 exposed.
thehackernews.com/2026/10/two-cvβ¦
threatlandscape.io/blog/ksmbd-zdiβ¦
