<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github-Actions on imsj</title><link>https://imsj-blog.pages.dev/tags/github-actions/</link><description>Recent content in Github-Actions on imsj</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 12 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://imsj-blog.pages.dev/tags/github-actions/index.xml" rel="self" type="application/rss+xml"/><item><title>GhostAction is back: fake "security audit" workflows stealing cloud and AI keys</title><link>https://imsj-blog.pages.dev/posts/ghostaction-github-workflows-return/</link><pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate><guid>https://imsj-blog.pages.dev/posts/ghostaction-github-workflows-return/</guid><description>&lt;p&gt;A lot happened this week: NetScaler and FortiMail zero-days, a KillSec ransomware takedown, a GitLab AI Gateway bug rated 9.9. The one I&amp;rsquo;d tell a developer friend about first is the GhostAction comeback, because it hits something I do every day: push to GitHub and trust that the workflows in my repo are mine.&lt;/p&gt;
&lt;p&gt;According to Socket&amp;rsquo;s write-up on 9 October, more than 500 GitHub accounts have committed a malicious workflow to tens of thousands of repositories since 7 October. It is an evolution of the GhostAction campaign first documented in September 2025.&lt;/p&gt;</description></item></channel></rss>