A fake LastPass download campaign abused GitHub's trusted reputation and poisoned Google search results to deliver the Rapuncel password-stealing malware to developer machines, exposing how brittle repository-based trust signals really are.
An examination of how cyber spies reportedly used GitHub-hosted malware to compromise EncroChat, and what the intrusion reveals about supply-chain abuse in espionage.
An analysis of the GitLost prompt injection vulnerability in GitHub’s Copilot Agent, showing how attackers could coerce the AI into exposing private repository data and how developers can defend against similar agentic security flaws.
Mozilla’s 0din research shows how AI coding agents like Claude Code can be manipulated through context injection in seemingly clean GitHub repositories to install malware, exposing a new class of developer workflow risk.
This post examines the TanStack npm supply chain compromise confirmed by Grafana, focusing on how malicious postinstall scripts stole GitHub tokens and enabled repository cloning, plus the practical defenses developers should apply.
Forked GitHub repositories can hide malicious changes, so this guide shows how to verify dependency integrity with checksums, signatures, and trusted sources.
An analysis of the GitBait phishing campaign showing how attackers abused GitHub Pages to target financial institutions and what developers can do to harden repositories against similar abuse.
A practical walkthrough of the package.json fields, lifecycle scripts, and dependency patterns I’m checking now to reduce npm supply-chain risk before GitHub’s automated script-install restrictions roll out.
A deep technical walkthrough of how to audit GitHub repositories for self-replicating malware, with indicators, propagation patterns, and defensive checks informed by the recent GitHub worm incident.
A technical breakdown of the Miasma Worm supply chain attack, analyzing how AI coding tools were used to compromise 73 Microsoft GitHub repositories and what the incident reveals about modern repository security risks.
A deep technical walkthrough of Microsoft’s findings on a Claude Code vulnerability that could expose GitHub credentials, with a defensive checklist for developers and security teams.
A deep technical walkthrough of the GitHub.dev one-click vulnerability that can expose full GitHub OAuth tokens, including how the attack works, what systems are affected, and how developers can defend against it.
A deep technical walkthrough of how GitHub OAuth implementations can leak tokens through single-click flaws, how to audit vulnerable flows, and how to harden them.
A developer-focused audit of the revenge-motivated Windows zero-day disclosure and GitHub ban response, with technical defensive checks and hardening steps for teams shipping on Windows.
A technical walkthrough of the alleged GitHub ban following a Windows zero-day disclosure, with developer-focused defensive steps for handling vulnerability reporting, account risk, and secure coordination.
A deep technical walkthrough of the Windows zero-day GitHub ban controversy, explaining the reported exploit behavior, the affected Windows attack surface, and the defensive steps security teams can take to detect and mitigate similar threats.
A deep technical walkthrough of GitHub's staged publishing changes for npm, how they disrupt scripted supply chain attacks, and what maintainers should do to harden release workflows.
A practical developer-focused checklist for locking down GitHub repositories after reports of source code theft, with concrete steps to reduce exposure, tighten access, and harden CI/CD workflows.
A deep technical walkthrough of how Megalodon malware rapidly automated the compromise of more than 5,500 GitHub repositories in under six hours, with a focus on the attack mechanics, affected developer workflows, and the defenses that actually reduce risk.
A deep technical walkthrough for auditing GitHub repository access, reviewing branch and token permissions, and rotating exposed secrets after reports of a breach involving 4,000 stolen internal repositories.
A technical walkthrough of how an internal GitHub repository breach can expose weak secret management, overbroad token scopes, and insufficient access controls, and how to audit and harden your own security posture.
GitHub’s breach via a malicious VS Code extension shows how compromised developer endpoints can expose internal repositories and cascade into broader supply chain risk.
Grafana Labs’ stolen GitHub token breach shows how a single compromised CI/CD secret can expose source code, trigger extortion, and put open-source supply chains at risk.
Grafana’s GitHub token breach shows how a CI/CD secret leak can expose source code, enable extortion, and turn pipeline weakness into a supply chain security incident.