Security Research
An ARTEX build ships no secret scanner. In our lab, it found the secrets anyway
An ARTEX build ships no secret scanner. In our lab, it found 8 of 9 planted secrets in seconds, even when asked only to assess the repo.
MOST POPULAR
all tags
other
An ARTEX build ships no secret scanner. In our lab, it found the secrets anyway
An ARTEX build ships no secret scanner. In our lab, it found 8 of 9 planted secrets in seconds, even when asked only to assess the repo.
Beyond ARTEX: 45 Agentic Attack Frameworks, What They Hunt For, and How to Find Them
~45 agentic attack frameworks beyond ARTEX, fingerprinted for internet scanning: dozens of operator consoles sit exposed today, many unauthenticated.
Claude Code settings.local.json Secrets: 17 months of exposure on GitHub, & Docker Hub
31,088 secrets in Claude Code’s .claude/settings.local.json on public GitHub, 5,343 valid at detection, 23,276 repositories. 613 more in Docker Hub images, 99 valid. Validity, timeline, Docker Hub, who is affected.
The Agents Have Now Found Your Secrets On GitHub: ARTEX Is Abusing Public Secrets Right Now
Microsoft Threat Intelligence caught attackers using an agentic AI framework, ARTEX, to hunt exposed secrets on public GitHub and move into Azure tenants in as little as five minutes. GitGuardian has tracked this attack path since 2017. Here is what changed, and four things to do today.
How to Handle Secrets in Helm
Kubernetes Secrets are base64 encoded, not encrypted, so a password in values.yaml is a working credential in Git. Compare four ways to keep secrets out of your Helm charts and find the one that fits what your team already runs.
Binance, BitGet, and the Credential Playbook That Keeps Working
The initial access vector changes, but the path stays the same: stolen credentials. Lessons from Binance and other recent crypto compromises.
Inside the LiteLLM hack: 153GB, 433,909 Files, 2,488 Organizations
Attackers dumped everything they harvested from LiteLLM builds during a 40-minute window in March. Here is what is inside and what it says about where secrets live.
What Is a High-Impact Leak? How to Rank Compromised Credentials by Real Risk
Validation-only triage misses 46% of critical secrets because they can’t be verified automatically. Here’s how to rank compromised credentials by what they can actually reach, and which leaks need containing the same day.
The Binance Hack Raises a Critical Question: What Can a Compromised Laptop Reach?
A compromised laptop may have started the Binance hack. What can an attacker reach from a developer’s machine?
Your Leaked Secrets Now Show Up in Wiz
GitGuardian now sends leaked secrets from GitHub, GitLab, Bitbucket, and Azure DevOps to Wiz once a day, with validity, severity, and a link back to the incident. Your cloud and AppSec teams see the same leaked key, and the secret value never leaves GitGuardian.
How GitGuardian Secures the Credential Layer: From Discovery to Remediation
Credential layer security is more than detection. Follow one credential through the GitGuardian platform, from discovery across repos, CI/CD, laptops, and vaults to owner and access context, safe remediation, and prevention.
GitHub Octoverse 2026: AI Agents, Citizen Developers, and the New Security Reality
GitHub’s Octoverse 2026 counted 34.3 billion commits, and over 40% of pull requests now start with an AI agent. Read to learn what the State of the Octoverse 2026 Report reveals about AI, citizen developers, and our new security reality.
