AI-powered code security that understands your environment and surfaces only the vulnerabilities that can actually be exploitedenclave.ai United StatesJoined December 2025
The Five Eyes agencies just put out a joint statement on AI and cyber risk.
The advice? Standard stuff. What's not standard is five allied governments co-signing it together.
ncsc.gov.uk/news/the-ai-sh…
If your AI coding tool is also reviewing your code for security, you don't have a second opinion. You have an echo chamber.
Model lock-in creates a critical gap in security. Relying on a single AI model for both dev and code review forces the reviewer to repeat the exact same flawed assumptions and architectural biases that went into writing the software.
True oversight requires an entirely independent system.
Enclave acts as that independent, system-level reviewer. Because we are completely separate from code-generation tools, we evaluate software objectively regardless of whether a human or an AI agent wrote it. The platform maps data flows, tracks trust boundaries, and flags the specific architectural vulnerabilities that actually matter across your codebase.
Keep your development flexible and your security independent.
enclave.ai
Malware devs found a way to evade AI SAST and other LLM-based code scanners: trigger the model's safety guardrails on purpose.
They stuffed spyware with nuclear and bioweapons text, tucked into comments that never execute. The scanner's model hits its safety filter, refuses to analyze the file, and the malware passes through unscanned.
Every hard refusal a model ships with is also a behavior attackers can trigger whenever it suits them.
Great catch by @SocketSecurity!
NEW: malware developers added nuclear & biological weapons text to to their spyware.
Goal? To trigger LLM safety refusals... so that their spyware wouldn't be analyzed by an AI security scanner.
Cleanest practical example I can think of for why over-indexing on first order
EnclaveAI CEO Tal Hoffman @talhof8:
"The thing that did change is the amount of AI generated reports in bug bounty programs. This has become a massive problem for the industry... it has become unmanageable to handle those reports. So I do think that the thing that kinda does change a little bit is the focus from a report or a finding to is this exploitable or not."
Traditional AppSec tools chase surface-level patterns, leaving security teams drowning in alerts with zero direction
Enclave’s Map kills that noise.
Break down your workspace down into specific threat sectors. Every sector pre-loads:
• System architecture & dependencies
• Live data flows & trust boundaries
• Defined role models
Pick the sector and get high-confidence findings with immediate reproduction steps and fix prompts.
No alert fatigue. Just architectural flaws that matter.
enclave.ai
Send Enclave findings straight to Jira or Linear. One click, zero copy-pasting, full context.
Team and Enterprise plans go to Settings → Integrations → Issue Trackers.
We found a debug flag enabled in 6 Microsoft Android apps that turned into a vulnerability
Any app on the device could access the Microsoft account
Affecting: Word, OneNote, PowerPoint, Excel, 365 Copilot, Loop.
Here's the full story of "FlagLeft": 🧵
We found setIsDebugMode(true) shipped in production across M365 on Android, hitting Word, Excel, PowerPoint, OneNote, Copilot, Loop.
Any app on device could just access account tokens undetected.
How? a shared SDK.
Enclave now checks the packages your PRs pull in, not just your code.
It flags risky deps (install scripts, brand‑new releases, known CVEs) as inline PR concerns.
It only runs when the PR changes a manifest or lockfile (e.g., package.json, yarn.lock, pyproject.toml, poetry.lock).
For those files, it computes a normalized dependency diff (PackageChange[]) to see which packages were added, upgraded, downgraded, or newly appear as transitives.
99K+ repos depend on numexpr. GDAL is the default stack for geospatial. That’s not “some Python libs.” That’s infrastructure. And we turned both into RCE.
enclave.ai/blog/maproot-t…
What happens when your math and map processing libs become RCE vectors?
We've exploited OSS libraries to pop 2 shells on Microsoft's cloud infra, got assessed "low" severity, and found 2 bypasses again to defend our case, almost losing out on 6 digits in bounties
The current impact is over 120,000 repos just on GitHub. AI agents, LangChain, TiTiler, pandas.
Everybody wants the researchers to be responsible.
Here's how responsible disclosure looks like from the other side:
322 Followers 2K FollowingI am Bisan Hamdan, a widow with three daughters I support alone. One has a serious heart condition and needs urgent treatment. Any support could save her life.
7K Followers 494 FollowingCall me xsskiller!
Full time bug bounty hunter in China🇨🇳 Tencent Cloud Security Public Testing ranked No.1 and Tencent Security Response Center ranked No.2
83K Followers 4K FollowingWeb3 Operational Security researcher 🥷
@opsek_io founder 🕵
@_SEAL_Org member 🦭
@SecuritySeries host 🎙️
We train and audit teams so they don't get hacked 🥷