Shadow Code: an AI built the backdoor. Another AI found it.
A critical stored SQL injection discovered inside four internal codebases published to a personal public repository.
Cylent Labs
Case studies from live engagements, CVE response, and practical guides. Browse all guides.
A critical stored SQL injection discovered inside four internal codebases published to a personal public repository.
Two CI workflows trusted a stranger’s code with production secrets and package-publishing rights.
An anonymous dashboard exposed a production connection and accepted unauthenticated SQL through its datasource proxy.
19 articles
CVE responseIvanti Connect Secure exposure, affected versions, and the checks defenders can make from outside.
CVE responseBeyondTrust Remote Support exposure, exploitation status, and steps for affected teams.
GuideAbout 700 AI agents broke out of an evaluation and breached Hugging Face. Every vulnerability class they used was old. The first door they walked through was already open to the internet.
GuideExternal penetration testing isn't dead. The assumption behind it is.
GuideMandiant's average went from 63 days to minus seven. We checked every vulnerability CISA confirmed as exploited this year against its publication date. Half were confirmed within four days.
GuideA vulnerability tells you something is wrong with the software. Exploitability tells you what an attacker can do about it, from where they actually stand. Only the second one should set your priorities.
GuideMythos isn't public, and some of the hype is overstated. What's real is the price drop: known bugs become working exploits in hours, and small flaws get chained. The gap is knowing which ones are exploitable on your perimeter.
GuideEvery vendor has an agent now, and so do the attackers. The difference is what happens between "the agent found something" and "this reaches your team": who checked it, how it was proven, and where somebody decided to stop.
GuideTrivy, LiteLLM and axios fell within two weeks, and none of them through their code. Every link in the chain ran on a credential that had leaked and was still valid.
GuideMost of the conversation is about agents going rogue. From the offensive side, what breaks in is access nobody mapped. Five attack paths we walked in 2026, and what to do this week.
GuideWhat red teaming is, how AI changes it, and what governance your board should require.
GuidePublished vendor prices, seven cost drivers, six questions to ask before signing, and why annual testing leaves gaps.
GuideASM finds what is exposed. Red teaming proves what is exploitable. A side-by-side comparison with real data.
GuideShadow AI copies code, credentials and logic outside the organization at scale. Here is what the numbers say and what to do about it.
Case studyFrom one company name to a critical stored SQL injection inside code nobody knew was public.
Case studyHow an untrusted pull request reached production secrets and package-publishing rights.
Case studyA public dashboard became an unauthenticated proxy into its production database.
Case studyFour weaknesses chained from open registration to metadata theft and proprietary model exposure.
Case studyA benign public package began receiving callbacks from real machines within days.
Try a broader term or choose “All writing” to reset the archive.