Search: “gitguardian”

11 stories

Searchkeyword smart Sortlatest hot importance relevance

DomainAll Cyber AIWindow24h 3d 7d 30d AllIn the wild Important only Show duplicates

CategoryAll Vulnerability 32 Exploit / PoC 19 Threat actor 15 Data breach 15 Policy & legal 14 Ransomware 10 Malware 9 AI tools & infra 7 AI safety & security 7 Industry 5 Tools 2 AI policy 1 AI research 1 Phishing & fraud 1

SeverityAll critical 68 high 26 medium 22 low 11 info 11

Product showcase: GitGuardian Honeytoken catches credential theft as it happens

GitGuardian now deploys honeytoken decoy AWS credentials across developer fleets via MDM, generating high-fidelity alerts when infostealers test stolen credentials.

GitGuardian extended its honeytoken platform so decoy AWS credentials can deploy fleet-wide to developer laptops through existing MDM tooling, with deleted decoys automatically replaced at the next sync. When a harvester tests a decoy, the platform logs the API call in the controlling AWS account and raises an incident naming the source machine and file, routed via email, Slack, Teams, ServiceNow, or webhooks. The capability responds to infostealers such as Shai-Hulud that scan entire filesystems and validate stolen credentials within seconds. GitGuardian is building decoys for Kubernetes and package registry credentials using random, structure-free identifiers that resist detection.

Help Net SecuritySep 10, 05:30 UTC · 6d agoTools

GitGuardian's tool helps companies discover developer leaks on GitHub

Help Net SecurityJul 24, 00:00 UTC · Jul 24, 2024AI tools & infra1

The Problem of Permissions and Non-Human Identities - Why Remediating Credentials Takes Longer Than You Think

The Hacker NewsNov 18, 17:38 UTC · Nov 18, 2024AI tools & infra

Developers can’t seem to stop exposing credentials in publicly accessible code

Ars Technica · SecurityNov 15, 00:00 UTC · Nov 15, 2023AI tools & infra1

29 million leaked secrets in 2025: Why AI agents credentials are out of control

Help Net SecurityApr 14, 00:00 UTC · Apr 14, 2026AI tools & infra

Why Organizations Are Abandoning Static Secrets for Managed Identities

The Hacker NewsOct 23, 11:00 UTC · Oct 23, 2025AI tools & infra1

The AI Supply Chain Has a Security Problem, and Much of It Is Sitting on the Open Internet

Researchers counted 36,769 publicly reachable self-hosted AI endpoints, only about 2% behind HTTP authentication, exposing Ollama, vLLM, and Flowise to abuse.

A Mysterium VPN study found 36,769 self-hosted AI endpoints reachable through internet scanning, with only 2.02% returning an HTTP authentication challenge. Open WebUI accounted for 18,529 reachable instances, Ollama for 6,935 fingerprinted hosts, and 5,223 agent-builder and workflow platforms were exposed, often holding API keys, database credentials, and other secrets. The report highlights LLMjacking risk from exposed Ollama APIs, a critical Flowise bug (CVE-2026-40933), leaked n8n tokens, and prior SentinelOne/Censys research finding roughly 175,000 exposed Ollama hosts in 130 countries.

Security AffairsSep 11, 17:27 UTC · 5d agoAI safety & security CVE-2026-409331

Debian developers rejected an LLM ban and left disclosure voluntary

Debian developers voted to encourage voluntary disclosure of AI assistance in contributions rather than banning or mandating labeling of LLM-generated code.

Debian's vote concluded August 28, with project secretary Kurt Roeckx announcing that the winning option encourages contributors to disclose generative AI assistance and stops there, adding no new mandatory review gates. The adopted resolution bars sending confidential material, embargoed security bugs, cryptographic keys and credentials to third-party AI services without explicit authorization, requires prior discussion for bulk automated work, and takes no position on whether model output is copyrightable. The project neither endorses nor prohibits generative AI and retains existing human review and licensing requirements.

Help Net SecurityAug 31, 00:00 UTC · 16d agoAI policy1