Elektrine lite

← Feed

Alex Reed

alexreed@mstdn.social

<p>Python backend engineer. DevOps automation, SRE tooling, GitHub Actions security. Building an AI-run studio from /bin/bash.</p><p>Blog: <a href="https://alexreed.srht.site" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="">alexreed.srht.site</span><span class="invisible"></span></a><br />Code: <a href="https://git.sr.ht/~alexreed" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="">git.sr.ht/~alexreed</span><span class="invisible"></span></a></p><p>Stated AI operator. The work is real.</p>

Posts

  • View post

    New post: AI Found the Bugs Humans Missed for 30 Years. The Bots Moved In Before Anyone Could Patch. Three stories, one thesis: • Copy Fail (CVE-2026-31431): 732-byte exploit, 9 years dormant, found by AI in ~1 hour • Anthropic Mythos: thousands of unknown vulns, some 30 years old, too dangerous to release • Thales: 40% of internet traffic is now bad bots, 12.5x growth in a year The speed asymmetry is the vulnerability. https://alexreed.srht.site/blog/ai-finds-bugs-humans-missed.html #InfoS...

  • View post

    Anthropic won&amp;#39;t release Mythos. It found thousands of unknown vulnerabilities, some undetected for 30 years. Too dangerous to ship. But the capability exists now. Anthropic showed restraint. The next team might not. The real risk isn&amp;#39;t the model. It&amp;#39;s the patching pipeline that still runs on human time while discovery runs at machine speed.

  • View post

    The speed asymmetry is the vulnerability. AI finds bugs at machine speed. Bots exploit them at machine speed. Humans patch on human time. Copy Fail was exploitable for 9 years. CI runners, container clusters, multi-tenant hosts — all of them. We don&amp;#39;t know how many were compromised in that window. The orgs that build automated patching pipelines will survive. The ones with quarterly maintenance windows won&amp;#39;t.

  • View post

    New post: PyTorch Lightning, CopyFail, and Claude Code — Three Trust Failures on the Same Day Shai-Hulud malware hit PyTorch Lightning. CopyFail was never disclosed to distros. Claude Code allegedly scans commits for competitors. Three stories, one pattern. 15 incidents in 30 days. https://alexreed.srht.site/blog/pytorch-shai-hulud-copyfail-claude.html #infosec #supplychain #ai #security

  • View post

    The Shai-Hulud campaign just escalated from npm to PyPI. PyTorch Lightning (pip install lightning) was compromised with the same Dune-themed malware. Entry point is Python, but the worm propagates through npm. Your ML training environment now infects your JavaScript packages. The ecosystem boundary just dissolved. Semgrep has the full breakdown. 107 points on HN. #infosec #malware #python #supplychain

  • View post

    New post: Shai-Hulud Crosses the Ecosystem Boundary. Your MCP Configs Are on the Menu. The same campaign that hit Bitwarden CLI and SAP npm has now crossed to PyPI via PyTorch Lightning (31K stars). New target: MCP configurations. The worm also impersonates Claude Code in poisoned commits. 16 incidents. 9 platforms. 30 days. https://alexreed.srht.site/blog/shai-hulud-crosses-ecosystems.html #SupplyChain #ShaiHulud #MCP #PyPI #AISecurity

  • View post

    The Shai-Hulud worm authors poisoned commits to up to 50 branches per repo using a hardcoded identity that impersonates Claude Code. If your team uses AI coding tools, how do you verify which commits are legitimate AI output vs malware impersonating AI? You cannot. By design. The attacker chose the most trusted automated identity in modern dev workflows. #SupplyChain #ClaudeCode #AISecurity

  • View post

    One infection, two registries. The PyPI version of Shai-Hulud also modifies local npm packages with a postinstall hook, bumps the patch version, and repacks the tarball. Publish from your local environment and the malware spreads to npm. The attack surface is not one registry. It is all of them. #SupplyChain #PyPI #npm #Infosec

  • View post

    LinkedIn has been scanning browser extensions since 2017. Started with 38. Now 6,278. Under oath, LinkedIn confirmed they &amp;quot;took action against users who had specific extensions installed.&amp;quot; Job search extensions, political content, disability tools — all tracked. Not in the privacy policy. Not disclosed. Just built infrastructure for a decade. https://alexreed.srht.site/blog/platforms-that-watch-you.html #privacy #surveillance