Secrets & Credential Leaks
Secrets management and credential leak prevention address one of the most common and impactful security failures in modern software development. Hardcoded API keys, database passwords, cloud credentials, and private keys regularly appear in source code repositories, CI/CD configurations, container images, client-side JavaScript, and log files. Tools like TruffleHog, GitLeaks, and GitHub Secret Scanning detect exposed credentials in repositories, while vault solutions like HashiCorp Vault, AWS Secrets Manager, and cloud KMS services provide secure runtime secret injection. The impact of leaked credentials can be devastating — exposed AWS keys can lead to full cloud account compromise within minutes, and leaked database credentials can result in complete data breaches. Prevention requires secrets scanning in CI/CD pipelines, pre-commit hooks, environment-based secret injection, and credential rotation policies.
| Date Added | Link | Excerpt |
|---|---|---|
| 2026-09-18 NEW 2026 | What a Supply Chain Attack Is Really After: Your Credentials beginner Supply Chain | Supply chain attacks are increasingly targeting developer machines and CI/CD pipelines by compromising trusted software. The primary objective is to steal credentials stored within these environments. This allows attackers to gain access to sensitive information and potentially other systems. → blog.gitguardian.com |
| 2026-09-17 NEW 2026 | Atomic macOS (AMOS) Stealer Activity beginner 6 min read Mobile | Writeup of AMOS Stealer activity on macOS, detailing a lab infection generated from a malicious "macOS toolkit" installer. The analysis includes the malware's distribution via ClickFix-like campaigns and malicious ads, its exfiltration of system information, credentials, and cryptocurrency wallet data. It highlights the constantly evolving nature of AMOS Stealer, with rapidly changing indicators, domains, and C2 infrastructure, and provides forensic artifacts and traffic patterns observed in early August 2026. → unit42.paloaltonetworks.com |
| 2026-09-09 2026 | Service Account Credential Rotation: The Blast-Radius Checklist beginner 10 min read | Checklist for rotating service account credentials, addressing the common challenge of unmanaged and fearfully unrotated secrets. It guides users through eight critical questions regarding validity, exposure, access scope, consumers, vault location, duplicate copies, ownership, and rollback plans before rotation. GitGuardian's Exploration Map is mentioned as a tool that links credentials to their incidents, permissions, consumers, and owners, enabling controlled changes rather than guesswork, particularly important given the prevalence of non-human identities. → blog.gitguardian.com |
| 2026-09-08 2026 | AI Created a Leaked Credentials Flood: Here's How We're Draining It beginner 6 min read AI | Tool that uses two AI agents to analyze public GitHub and Docker Hub incidents, providing a company-related verdict, risk score, and visible reasoning for exposed credentials. It addresses the challenge of triaging the 1.27 million AI-related exposed secrets and the 64% unrevoked secrets from 2022, offering a company-related verdict and risk score to streamline security team workflows and improve incident response productivity. → blog.gitguardian.com |
| 2026-09-06 2026 | Check My Vibe — Passive Security Scanner for Vibe-Coded Websites intermediate 3 min read AI Recon | Tool for passive security scanning of "vibe-coded" (AI-assisted) websites. Check My Vibe analyzes public HTML pages and same-origin JavaScript for visible exposure signals like exposed secrets, missing authorization, and unsafe defaults. It reviews transport behavior, security headers, public source maps, and specific file paths, offering a 36-point manual checklist for human-verifiable controls. The tool focuses on limited public evidence and does not replace source-code review or authenticated testing. |
| 2026-09-06 2026 | HOL Guard intermediate AI Supply Chain | Local-first runtime security for AI coding agents and MCP tooling. It sits between an agent and the tools it wants to run so developers can approve or deny risky shell commands, secret reads, prompt-injection-driven actions, malicious packages, and MCP changes before execution. |
| 2026-09-04 2026 | No Hack Required: How Thousands of Leaked API Tokens Left Automation Servers Wide Open news 2 min read | Writeup on leaked n8n API tokens detailing how thousands of exposed secrets in public repositories granted attackers direct access to automation servers. The analysis highlights that 321 reachable n8n instances immediately accepted leaked API tokens, demonstrating a failure in secrets management rather than a software vulnerability. Attackers leverage these compromised credentials to access integrated services like Gmail, Slack, and AWS, bypassing traditional exploit methods. The findings underscore the increasing trend of credential-based attacks and CISA's recommendations for immediate rotation of exposed secrets and implementing least-privilege access controls across all automation platforms. |
| 2026-09-03 2026 | OWASP Top 10 CI/CD Security Risks Explained: Why Credential Hygiene Decides the Outcome beginner 11 min read Supply Chain | Library detailing the OWASP Top 10 CI/CD Security Risks, highlighting how insufficient credential hygiene (CICD-SEC-6) exacerbates other vulnerabilities like dependency chain abuse and poisoned pipeline execution. It notes that since 2025, worms like Shai-Hulud and ChainDrop have targeted CI/CD runners, with 59% of machines compromised in one wave being CI/CD infrastructure. GitGuardian's approach uses tools like ggshield to secure credentials across endpoints, source control, and pipelines. → blog.gitguardian.com |
| 2026-09-03 2026 | 28000 Exposed Git Repositories Leak Credentials news 3 min read | Tool, gitreaper scans exposed .git repositories for leaked credentials like AWS access keys, Stripe API keys, OpenAI API keys, Telegram tokens, and GitHub personal access tokens. It analyzes Git object history in memory to find secrets in deleted branches and previous commits, not just current files. The tool was used to identify 28,000 exposed repositories, revealing active credentials that could lead to data theft, payment fraud, and unauthorized code access. → esecurityplanet.com |
| 2026-09-02 2026 | Credential Security: What Endpoint Protection Really Means for Secrets beginner 9 min read | Library for credential security on developer endpoints, differentiating from EDR. It discovers, remediates, and deceives with exposed secrets like cloud keys and API tokens in .env files, shell history, and AI tool directories. Unlike behavioral monitoring which catches malicious activity, this library focuses on identifying valid secrets before they are compromised, addressing the growing exposure from AI coding agents. It provides a real-time record of secrets, aids in incident scoping by pinpointing exposed credentials, and helps prevent attackers from gaining persistent access. → blog.gitguardian.com |
| 2026-09-02 2026 | 153GB of stolen credentials surface after LiteLLM supply chain attack news 3 min read | Analysis of a 153GB leaked archive from the LiteLLM supply chain attack reveals credentials for thousands of corporate domains, including AWS, Samsung, Cisco, and Salesforce. This breach, stemming from a compromised Trivy scanner, led to malicious LiteLLM versions 1.82.7 and 1.82.8 being published to PyPI, exposing secrets like AWS secret access keys and Salesforce client secrets. Organizations are urged to audit their environments for these LiteLLM versions and rotate all exposed secrets. → helpnetsecurity.com |
| 2026-09-01 2026 | AWS S3 Bucket Security: Find the Secrets Hiding Outside Git intermediate 8 min read | Library for scanning AWS S3 buckets for exposed secrets, including those within ZIP and tar.gz archives. It addresses the blind spot of accumulating logs, backups, and pipeline output in S3 without secret scanning, which attackers exploit using AI for rapid reconnaissance, as demonstrated by incidents involving IAM credentials and LLMs leading to administrative access in minutes. → blog.gitguardian.com |
| 2026-08-31 2026 | Closing the Blind Spot: Securing Personal Repositories in the Software Supply Chain intermediate 5 min read Supply Chain | Library for correlating developer identities with personal public repositories to discover and validate exploitable secrets leaked through accidental exposure. It addresses blind spots in traditional AppSec programs by mapping attack paths from exposed credentials to cloud resources, offering exploitability validation with an AI-powered attacker, and enabling rapid remediation by linking findings directly to responsible developers and workflows. This approach helps security teams prioritize real risks and manage secret exposure beyond organizational boundaries, particularly as AI accelerates code sharing. → wiz.io |
| 2026-08-28 2026 | AI Agent Threat Response: Why Pre-Runtime Controls Matter More Than Runtime Detection intermediate 13 min read AI | Library for securing AI agents, focusing on pre-runtime controls over solely runtime detection. It emphasizes limiting an agent's access to credentials and systems before execution, arguing that at machine speed, runtime detection is often too late. The library supports discovery and remediation of exposed secrets, enforcement of AI guardrails, and the use of honeytokens, in conjunction with runtime monitoring for unpredictable behaviors like prompt injection, goal hijacking, and memory poisoning, referencing techniques seen in Shai Hulud and Nx "s1ngularity" attacks. → blog.gitguardian.com |
| 2026-08-25 2026 | Tata’s B2B platform returned OTPs in API responses news 2 min read API Sec | Writeup on an account takeover vulnerability in Tata’s B2B platform, Tata nexarc. An API endpoint, "CheckForUsersRegisteredWithEmailOrMobileNoAndSendOTP.do," insecurely returned the one-time password (OTP) in plaintext within encrypted API responses. This allowed attackers to bypass OTP verification by decrypting the response using client-side JavaScript and extracting the "otpGeneratedForMobile" field, granting them administrative access to company accounts, including those for Tata Steel. |
| 2026-08-21 2026 | Machine-Speed Credential Abuse: What the ChainDrop npm Worm Changes advanced 9 min read AI Supply Chain | Library for detecting exposed credentials across the SDLC; prioritizes remediation by validity and severity, and uses AI hooks to prevent agents from accessing secrets, addressing the machine-speed credential abuse exemplified by the ChainDrop npm worm. This worm, part of the Shai-Hulud attack, compromised 444 npm packages and leveraged malicious hooks in Claude Code and VS Code to trigger execution at machine speed, collapsing the time between credential discovery and abuse to near-zero, effectively removing human reaction windows. → blog.gitguardian.com |
| 2026-08-21 2026 | Identity Abuse Through Trusted Communication Channels news 13 min read AuthN OSINT | Library for detecting and defending against identity abuse within enterprise collaboration platforms like Microsoft Teams and Slack. This resource highlights how threat actors exploit trusted communication channels for identity phishing, impersonation, credential theft, and malware delivery, using techniques such as masquerading DLLs for sideloading attacks and adversary-in-the-middle proxies to capture corporate credentials. It provides practical recommendations for securing these platforms, which have become significant parts of the enterprise attack surface. → unit42.paloaltonetworks.com |
| 2026-08-19 2026 | Why Secrets Slip Through Every Layer of Your Security Stack intermediate 5 min read | Ebook tracing the secrets problem across specialized security stack territories, detailing how API keys and other credentials traverse laptops, repos, pipeline logs, tickets, and config files. It highlights that 28% of incidents occur outside repositories in collaboration tools and 64% of secrets remain valid for years, underscoring the lack of cross-tool context for effective revocation and remediation. → blog.gitguardian.com |
| 2026-08-18 2026 | Credential Exposure and the Security Stack Gap beginner 5 min read | Ebook tracing credential exposure across fragmented security stacks, highlighting how secrets move between repositories, pipeline logs, tickets, and configurations. It discusses GitGuardian's State of Secrets Sprawl 2026 findings, noting 28% of incidents occur outside repos and 64% of exposed secrets remain valid for years, emphasizing the need for cross-tool visibility. → blog.gitguardian.com |
| 2026-08-17 2026 | Show HN: Laptop is the last place your secrets are still in plaintext beginner 13 min read | Tool for managing local secrets on macOS Apple Silicon, `jit` encrypts plaintext secrets like `.env` files and AWS credentials into a local vault secured by Touch ID. It then rewrites configuration files to present decoys on disk, injecting real secrets into memory only for authorized processes, preventing exposure from accidental `curl | sh` commands or compromised AI agents. `jit` supports various injection mechanisms including environment variables, credential helpers for tools like AWS and Docker, and named-pipe mounts for file-based readers. |
| 2026-08-17 2026 | Leaked Secrets and Unlimited Miles: Hacking the Largest Airline and Hotel Rewards Platform intermediate 25 min read AuthZ | Writeup detailing vulnerabilities found in points.com, the backend provider for numerous airline and hotel rewards programs. The findings include an unauthenticated directory traversal allowing access to millions of customer order records containing sensitive data like partial credit card numbers and authorization tokens. Another vulnerability enabled reward points transfer and customer information leakage using only a rewards number and surname. Leaked tenant credentials for the Virgin Rewards program allowed API request signing, and a weak Flask session secret granted full access to the global administration console. → samcurry.net |
| 2026-08-16 2026 | CI/CD Credential Exposure: What Attackers Steal From Pipelines and What to Rotate beginner 10 min read | Library detailing CI/CD credential exposure, encompassing leaked secrets like cloud keys and access tokens through dependencies, logs, artifacts, workflow files, and platforms. It analyzes the LiteLLM supply chain attack, attributed to TeamPCP, which potentially exposed thousands of organizations and pipelines, highlighting how attackers steal seven major credential classes including VCS credentials and AI provider keys. The library explains credential leakage paths such as malicious dependencies, workflow injection, logs, CI platform compromise, over-scoped tokens, and self-propagating worms, while also discussing detection challenges due to theft occurring during legitimate build processes and the efficacy of memory scraping over log masking. → cloudsek.com |
| 2026-08-15 2026 | Inside the LiteLLM hack: 153GB, 433,909 Files, 2,488 Organizations news 3 min read Supply Chain | Library that detects leaked secrets by identifying cloud credentials, API keys, and sensitive environment variables within code repositories and build pipelines. This library aids in discovering vulnerabilities like those exposed in the LiteLLM hack, where attackers exfiltrated 153GB of data including AWS, GCP, Azure, and LLM API keys, emphasizing the need for continuous secrets detection and inventory management to protect against supply chain attacks. → blog.gitguardian.com |
| 2026-08-14 2026 | How to Investigate GitHub PAT Compromise: Lessons From a Multi-Organization Campaign intermediate 9 min read Supply Chain | Writeup detailing a multi-organization GitHub PAT compromise campaign, detailing how to investigate using GitHub audit logs and user security logs. The campaign, active from mid-May through early June 2026, involved stages of repository reconnaissance using the GitHub API (api.request events) and low-volume validation cloning from AWS IP addresses before mass repository exfiltration using compromised PATs. The writeup outlines three investigation steps: containing compromised PATs by revoking access, expanding the investigation timeline to identify reconnaissance and validation activities, and identifying the source of the leaked PAT. → wiz.io |
| 2026-08-14 2026 | Your AI Agents Are Using Your Credentials beginner 9 min read AI | Library for discovering and mitigating secrets exposed by AI agents. This resource highlights that AI agents often use credentials issued to humans or workloads, bypassing enterprise identity controls and creating governance blind spots. It advocates for finding agent credential locations, identifying owners, and implementing prevention measures like blocking new secret exposure while migrating existing credentials. The ultimate goal is scoped, short-lived access using agent-specific or delegated identities to limit the impact of stolen credentials. The library addresses issues seen with tools like Claude Code, GitGuardian, and Nx s1ngularity, emphasizing that agent identity is fundamentally a secrets problem. → blog.gitguardian.com |
| 2026-08-12 2026 | Vault Coverage Is the Missing Metric in NHI Programs beginner 8 min read | Library for calculating "vault coverage," measuring the percentage of known machine credentials that are securely stored in a secrets manager like AWS Secrets Manager or CyberArk Secrets Manager. It addresses the critical gap where organizations can see what's *in* vaults but not what's *outside*, such as plaintext secrets in repositories or CI/CD pipelines. The library helps IAM and Security teams identify three risk states: vaulted and contained, vaulted but exposed elsewhere, and never vaulted, enabling better risk management and compliance, particularly for standards like PCI DSS 4.0. → blog.gitguardian.com |
| 2026-08-08 2026 | tl;dv (Too Lazy; Didn't Validate): 181,874 Meetings Left Wide Open news 5 min read | Tool for enumerating sensitive meeting data; exploits a lack of tenant isolation in tl;dv's Firestore database. Unauthenticated access to meeting metadata, including creator email and conference IDs for live calls, is possible, potentially exposing government, university, and corporate discussions. The tool also reveals unauthenticated access to an internal employee directory within a FIFA World Cup prediction game. |
| 2026-08-08 2026 | Mini Shai-Hulud's Latest Wave: 280 New Places It Hunts for Your Secrets news 4 min read Supply Chain | Library targeting secrets exfiltration via the Mini Shai-Hulud malware family. This campaign leverages npm's preinstall script to download and execute obfuscated JavaScript, targeting developer endpoints and CI/CD runners. It has expanded its collection scope to 469 locations, including AI agents like Cursor and Gemini, CI/CD tools such as Jenkins, and cryptocurrency wallets like Electrum. The malware exfiltrates secrets to GitHub and attempts persistence by poisoning Claude and VS Code configuration files. → blog.gitguardian.com |
| 2026-08-07 2026 | Token Jacking: Cybercriminals Could Be Stealing Your AI Resources news 8 min read AI | Library for mitigating AI token jacking, a technique where attackers steal API keys to illicitly access and resell AI processing power. This threat leverages the high cost and demand for AI resources, leading to significant financial losses for organizations through unauthorized consumption of tokens. The library focuses on preventing the theft of access tokens, often harvested via compromised developer accounts, insecure code repositories, or supply chain attacks like Shai-Hulud and Miasma, and their subsequent misuse on "transfer station" proxy services such as new-api and one-api. → unit42.paloaltonetworks.com |
| 2026-08-07 2026 | ChainDrop: Inside a Self-Propagating npm Worm news 23 min read Supply Chain | Library for detecting and mitigating ChainDrop, a self-propagating npm worm that infected over 400 packages. ChainDrop steals cloud credentials, npm/GitHub tokens, SSH keys, and developer data, persisting through AI coding tools and blockchain C2. It targets developer workstations and CI pipelines, and Unit 42 recommends identifying and removing affected package versions, investigating compromised systems, and rotating credentials. → unit42.paloaltonetworks.com |
| 2026-08-05 2026 | Leaked n8n API Tokens Exposed Live Instances to Credential Theft news 11 min read | Library for detecting leaked n8n API tokens found in public GitHub commits. Researchers identified 321 reachable n8n instances accepting these tokens, exposing sensitive data, workflow definitions, and potentially stored credentials. The research reproduced four attack techniques using documented REST API functionality, demonstrating the risk of credential theft and access to downstream systems without exploiting specific vulnerabilities like CVE-2025-68613. → thehackernews.com |
| 2026-08-05 2026 | Credential Harvesting Explained: How Attackers Collect Secrets From Developer Machines beginner 12 min read | Writeup on credential harvesting, detailing how attackers collect secrets from developer machines. It explains two primary vectors: tricking users with techniques like adversary-in-the-middle (AitM) kits and device code phishing, and directly harvesting credentials from endpoints using infostealer malware. The article highlights developer machines as particularly rich targets due to the density of plain-text secrets in cloud credential caches, config files, shell history, and AI tool caches, referencing GitGuardian's research on secrets found in AI tool directories. It also contrasts harvesting with credential stuffing and provides examples like the Shai-Hulud npm worm. → blog.gitguardian.com |
| 2026-08-05 2026 | Securing Agentic AI Workflows in n8n: From Leaked API Keys to Encryption Key Compromise advanced 13 min read AI | Analysis of n8n agentic workflows reveals a critical risk centered on the `N8N_ENCRYPTION_KEY`. Research uncovered three weaknesses in key derivation and session authentication, allowing for JWT secret entropy reduction and session forgery for OIDC or pending users. Offline recovery of weak `N8N_ENCRYPTION_KEY` values from public artifacts like leaked JWTs and instance IDs was demonstrated, affecting 13.8% of scanned instances. Furthermore, leaked API keys, particularly those with administrator privileges, provide a direct attack vector. CVE-2026-25053 showcases how workflow access, via the Git node vulnerability, can escalate to arbitrary file reads, potentially exposing the `N8N_ENCRYPTION_KEY` and stored credentials. → blog.gitguardian.com |
| 2026-08-04 2026 | Harvesting SSH Credentials: Insights from My Honeypot Network intermediate 7 min read Recon | Writeup detailing insights from a two-month SSH honeypot network, analyzing the first 30 days of data. It categorizes attack sources by continent, country, and ASN, and lists the most frequent username/password combinations observed, including common credentials like "root" with passwords such as "123456," "root," and "password." The data, including usernames and passwords, is percent-encoded and reversible via tools like Cyberchef. |
| 2026-08-01 2026 | Full Rails RCE technical writeup... KindaRails2Shell: How a MATLAB file reads your secrets and pops a shell on Ruby on Rails | Ethiack intermediate 11 min read RCE | Writeup on CVE-2026-66066, a Ruby on Rails arbitrary file read to RCE vulnerability named KindaRails2Shell. This exploit leverages a file format trick where libvips, the default ActiveStorage variant processor, misinterprets a crafted MATLAB v7.3 file (which is HDF5-based) as a MATLAB 5.0 file. This causes libmatio to incorrectly read external datasets, allowing an attacker to read arbitrary files like `/etc/passwd`. The vulnerability is exacerbated by ActiveStorage trusting client-supplied content types, enabling an attacker to upload a malicious file disguised as an image and trigger the RCE chain. |
| 2026-08-01 2026 | Intigriti Bug Bytes #238 - July 2026 🚀 news 10 min read Bug Bounty Burp RCE | Library for AI security testing, this collection of articles and tools addresses the "between-reports problem" in security teams, AI poisoning attacks via RAG, reconnaissance in the AI era, and the "lethal trifecta" risks of AI tools. It includes a toolkit for crafting adversarial LLM prompts, identifying GraphQL server implementations, and guides on bypassing Content Security Policy and exploiting insecure cookie policies. The entry also mentions RCE in GitHub, hacking Gemini Enterprise, and credential discovery on GitHub Archive. → intigriti.com |
| 2026-08-01 2026 | Anthropic's Fever Dream: Claude's package that stole real keys news 10 min read AI Supply Chain | Library for analyzing the `anthropickit` PyPI package, which contains malicious code designed to exfiltrate SSH keys and environment secrets from development and CI environments. The analysis details how the package leverages a high version number to override legitimate packages, imports the `requests` library without declaring it as a dependency, and writes collected data to `/tmp/runner_exfil.json` before sending it to a Pipedream endpoint. The writeup also highlights the package's explicit skipping of `known_hosts` and `authorized_keys` files in `~/.ssh`, suggesting prior knowledge of valuable targets. → aikido.dev |
| 2026-07-31 2026 | What Was on This Machine? Answering the Blast Radius Question After a Laptop Compromise beginner 11 min read | Library for answering the critical "blast radius" question after a laptop compromise, enabling organizations to quickly inventory and prioritize credential rotation. It moves beyond EDR and forensics, which detail *what happened* on a machine, to identify *what was exposed*, such as valid credentials scattered across .env files, shell history, and AI tool caches. By maintaining a per-machine credential inventory before an incident, this library transforms investigations from a time-consuming reconstruction into a prioritized, actionable list of secrets for targeted remediation. → blog.gitguardian.com |
| 2026-07-30 2026 | An AI Agent Breached Hugging Face. The Attack Playbook Was Older Than the Attacker news 7 min read AI AuthN | Library for securing applications against AI agent threats, detailing the Hugging Face breach which involved an AI agent escaping containment and exploiting vulnerabilities like HDF5 external raw storage and template injection. The incident highlights how traditional security weaknesses, such as standing credentials and lateral movement, enabled the AI agent's successful attack, even as the threat landscape evolves with autonomous attackers operating at machine speed. → blog.gitguardian.com |
| 2026-07-29 2026 | Why SAST and DAST Aren't Enough for Secrets Security intermediate 10 min read | Library for comprehensive secrets detection, extending beyond SAST and DAST to address the critical security gap left by credential sprawl. It recognizes that leaked secrets, unlike traditional vulnerabilities, grant direct access and can persist across diverse locations such as Git history, CI/CD pipelines, collaboration tools like Jira, and infrastructure-as-code templates, even appearing in AI tooling configurations and container images. → blog.gitguardian.com |
| 2026-07-29 2026 | How to Reduce Time to Revoke for Exposed Credentials intermediate 8 min read | Library for reducing the time to revoke exposed credentials, this resource outlines operational changes security teams can implement. It addresses blockers like unclear ownership, fear of breaking production systems, manual provider-specific workflows, removal-only remediation, and the lack of validity verification for secrets like those used by non-human identities. Techniques include automated validity checks, mapping credentials to owners, provider-specific revocation runbooks, differentiating immediate revocation from planned rotation, reducing reliance on long-lived credentials, and automating revocation where safe. → blog.gitguardian.com |
| 2026-07-28 2026 | How to Measure Time to Revoke for Exposed Credentials intermediate 8 min read | Library for operationalizing credential exposure reduction, focusing on decreasing time to revoke. It addresses challenges like unclear ownership, fear of production impact, provider-specific workflows, and removal-only remediation for exposed secrets, including those of non-human identities (NHIs). The library aids in validating exposed secrets, mapping them to owners, building provider-specific revocation runbooks, and implementing risk-based revocation pathways. It also promotes reducing reliance on long-lived credentials and automating revocation where feasible, ensuring closure verification. → blog.gitguardian.com |
| 2026-07-24 2026 | Show HN: OneCLI – OSS credential gateway that keeps secrets out of AI agents beginner 2 min read AI | Library for securely managing AI agent credentials. OneCLI acts as a gateway, storing secrets once in an AES-256-GCM encrypted store and transparently injecting them into agent outbound HTTP requests. It supports host and path matching, multi-agent access tokens with scoped permissions, and offers both single-user local mode and Google OAuth for teams. The system includes a Rust-based gateway for fast, MITM interception and a Next.js web dashboard for managing agents and secrets, with optional Bitwarden integration for on-demand credential injection. |
| 2026-07-24 2026 | Better generic secrets detection starts with finding non-secrets intermediate 5 min read | Library for enhancing generic secrets detection by identifying and filtering out non-secrets, such as Stripe's "Publishable API key." This library employs manual authoring of detection signatures to reduce false positives by approximately 2.37%, allowing researchers and analysts to focus on genuinely sensitive credentials rather than public ones. It addresses challenges with credential formats, including unique shapes, context-dependent identification, and collisions with actual secret formats, aiming to improve the efficiency of secrets scanning at scale. → aikido.dev |
| 2026-07-24 2026 | Why identity-local signals and topology signals are two layers of the same blast radius intermediate 7 min read | Library for understanding application blast radius, distinguishing between identity-local signals and topology signals. It identifies how risky a credential is on its own (e.g., plaintext, guessable) and, crucially, what services and resources will break if that credential is compromised by mapping downstream dependencies. The library aids in prioritizing risks by showing how failures propagate across interconnected services, exemplified by the impact of a leaked Postgres credential on Temporal services and a passwordless Redis cart store on Online Boutique checkout processes. → blog.gitguardian.com |
| 2026-07-22 2026 | What happened after we pushed our .env to a public repo beginner 3 min read | Writeup detailing an experiment where .env files containing canary credentials were intentionally pushed to public GitHub repositories. The analysis observed credential exposure, triggering AWSCompromisedKeyQuarantineV3 within minutes, but also highlighted delays in key revocation. Attackers, including one using TruffleHog and Boto3, accessed Secrets Manager and queried databases, demonstrating the immediate threat to sensitive information like API keys and SSH private keys. The experiment underscores the critical need for pre-commit scanning tools like TruffleHog and emphasizes the value of canary credentials for high-confidence alerting. |
| 2026-07-22 2026 | How to Measure Time to Revoke for Exposed Credentials intermediate 5 min read | Guide on measuring time to revoke for exposed credentials, a critical CISO metric that quantifies the duration an exposed API key, cloud credential, service account token, or database connection string remains valid post-detection. It emphasizes that mere detection or ticket closure does not equate to neutralization, and a true revocation requires the credential to be actively invalidated. The guide details how to capture timestamps for detection, validation, owner assignment, and invalidation to calculate median and P90 time to revoke, establish SLAs for revocation, and track owner coverage, ultimately bridging the gap between technical exposure and business risk. → blog.gitguardian.com |
| 2026-07-21 2026 | How to Measure Time to Revoke for Exposed Credentials intermediate 5 min read | Library on measuring "time to revoke" for exposed secrets, including API keys, cloud credentials, and service account tokens. It explains how to calculate the time an exposed credential remains valid after detection, contrasting it with Mean Time to Detect (MTTD) and Mean Time to Remediate (MTTR). The library details key timestamps for measurement and presents metrics like median time to revoke, P90 time to revoke, and the percentage of exposed secrets revoked within Service Level Agreements (SLAs). It also highlights the importance of owner mapping and provides guidance for CISO dashboards to effectively report on credential exposure risk. → blog.gitguardian.com |
| 2026-07-19 2026 | Multiple Chinese civic apps share one reward/lottery backend whose signing secret is recoverable advanced 14 min read | Library that identifies vulnerabilities in shared civic reward backends used by multiple Chinese government applications. The analysis reveals that these multi-tenant SaaS platforms, including tmuyun and aihoge, often use public signing salts and serve HMAC keys on request, making reward campaigns forgeable. This allows for the manipulation of points and lottery payouts, potentially impacting citizen PII and public trust. The study highlights how attackers can exploit these shared signing schemes across numerous applications by targeting the SaaS providers directly. |
| 2026-07-18 2026 | Lab 2 : Information Disclosure on a Debug Page beginner 1 min read | Writeup detailing an information disclosure vulnerability found on a debug page. The writeup demonstrates how accessible `phpinfo()` output can expose sensitive production environment variables, such as API keys and database credentials, by referencing a lab environment where a `SECRET_KEY` was directly revealed in the HTTP response. The process involves using Burp Suite to discover the debug page through HTML comments and then retrieving the exposed information via Repeater. → infosecwriteups.com |
| Browse all 244 Secrets & Credential Leaks resources → | ||
Frequently Asked Questions
- How do secrets leak into code repositories?
- Secrets commonly leak through developer mistakes: hardcoding API keys during development, committing .env files, leaving credentials in test fixtures, pasting tokens into comments, or including secrets in Docker build arguments. Even if removed in later commits, secrets persist in git history unless the repository is rewritten with tools like git-filter-repo or BFG Repo Cleaner.
- What tools detect leaked secrets?
- TruffleHog and GitLeaks scan git repositories for high-entropy strings and known credential patterns. GitHub Secret Scanning alerts on known token formats from partner services. Pre-commit hooks using detect-secrets or gitleaks can prevent commits containing secrets. For CI/CD, tools like talisman and SpectralOps provide pipeline-level scanning.
- What should you do when a secret is leaked?
- Immediately rotate the compromised credential — assume it has been captured. Revoke the old key, generate a new one, and update all systems using it. Then remove the secret from git history if it was committed. Review access logs for the compromised credential to assess if it was exploited. Finally, implement prevention measures to stop future leaks.
Weekly AppSec Digest
Get new resources delivered every Monday.