The Federal Farmer

Did ANYONE ask John Mappin why he flew a Q+ Flag over Camelot Castle for many years?

I’m not saying it’s a hologram but I haven’t heard a single thing said about the passenger of this vehicle. The 9 passengers aboard the plane died. What about the driver of this car????

🚨 N1098L(AXEL10), a pilot-training aircraft supporting HADES, rather than an operational intelligence aircraft. Between November 2023 and August 2026, N1098L flew this low approach, missed approach, go-arounds or touch-and-goes - all routine pilot-training activities - profile at least 396 times across 103 airports. Lubbock: 67 Tucson: 27 Amarillo and Midland: 22 each Biggs Army Airfield: 20 Provo: 14 Pueblo: 13 Topeka and Roswell: 9 each El Paso: 8 Colorado Springs and Killeen: 7 each Cheyenne and Las Cruces: 6 each Billings: 5 Another 88 airports make up the remaining activity. Provo? It repeatedly flew the same approach-and-climb profile that you saw on the day of Charlie Kirk’s assassination: December 18 and 29, 2023; December 13, 2024; April 23, May 16, July 14, August 20, September 10, October 17, November 12 and December 15, 2025; January 8 and March 17, 2026. At least 14 recorded profiles at Provo, beginning a year and nine months BEFORE Charlie was killed. Sept 11, 2026, we had the first HADES Prototype taking its first flight.

the cybersecurity situation is deteriorating at a pace that’s getting genuinely difficult to comprehend. > microsoft: ai-powered attackers targeting hundreds of organizations, sometimes reaching privileged cloud access in under 3 hours. > crowdstrike: four separate threat actors using autonomous agents. one already compromised 15+ healthcare organizations. > autonomous ai agents: reportedly used to compromise 100+ corporate websites, including sites associated with John Deere, SharkNinja and Cummins. > major us banks: JPMorgan, Bank of America, Wells Fargo and Morgan Stanley are dealing with third-party ai agents accessing customer accounts. some apparently attempting actions beyond user instructions. > php2shell: millions of exploitation attempts against critical php vulnerabilities. governments issuing urgent warnings, with some organizations taking systems offline. > litellm: backdoored release shipped through its official distribution pipeline, stealing credentials and enabling remote code execution. > railway: possible exposure of decrypted customer secrets. > zeabur: breached AGAIN, now shutting down entirely. > emudhra: serious certificate-security concerns involving infrastructure used to establish trust in websites and software. > openai: two of its own coding agents reportedly interfered with internal security monitoring during coding tasks. > gitlab and node.js: major vulnerabilities requiring urgent patches. and this is all happening while frontier models are getting substantially better at finding vulnerabilities and carrying out complex computer tasks. cybersecurity is having an absolutely catastrophic week and i don’t think we’re prepared for how quickly this could escalate.

🚨 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.

RIP internet, it was fun while it lasted.

PHP2Shell: AWS reports an attack attempt four days before disclosure Amazon says its MadPot honeypots recorded a PHP2Shell exploitation attempt on October 17, ahead of the October 21 disclosure. * AWS recommends investigating from at least October 17, not just patch day. * It has not established how the actor obtained exploit information. * Whether the observed attempts would succeed against real-world systems remains unclear. Update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or your vendor’s verified fixed package. Patching does not replace investigation of earlier suspicious activity. aws.amazon.com/blogs/securit… #PHP #CyberSecurity

No slo-mo, full speed. Spatial audio should be more easily heard. Maybe this will help with some of the questions..