AI-powered code security that understands your environment and surfaces only the vulnerabilities that can actually be exploited

Joined December 2025
18 Photos and videos
Connect Enclave to Claude in one click, then get your findings, PR scan status, and threat models right where you work.
2
7
48
Enclave retweeted
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 safety alignment is risky. When closed (and open) models ship with aggressive refusals, they will be sprinkled with second-order blindspots that attackers will discover...and exploit. We are only in the earliest days of attackers leveraging these features, and it wouldn't surprise me if users systems that need to handle complex cybersecurity issues demand that models be less safety-blunted. In the weeds: @SocketSecurity's post also shows why intention matters in how you design a malware analysis pipeline to avoid prompt manipulation. H/T to colleagues that shared this with me socket.dev/blog/mini-shai-hu…
3
11
592
Enclave retweeted
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."
1
6
7
688
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
3
70
[NEW FEATURE] Cloud deployed or self-hosted? Enclave now supports GitHub Enterprise or GitLab. Settings → Connections.
8
88
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.
1
8
119
Enclave retweeted
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": 🧵
6
6
41
5,394
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.
3
1
9
428
👏 @Yanir_ & @ofekdavidlevin on the finding
3
75
Enclave retweeted
Exclusive: How One Line of Code Put Billions of Microsoft Android App Downloads at Risk securityweek.com/exclusive-h…

1
3
11
1,228
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.
1
2
13
325
Enclave retweeted
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:
4
33
171
11,894
Cloud-Based Criticality is live. Enclave now ranks every finding by what your AWS setup actually allows. Reasoning is attached and severity is in context, not in theory. Go to Settings → Connections → AWS on Enclave.ai
1
9
519
Software has entered a supply and demand crisis. AI-driven velocity means more code hits your repositories than your team can peer review. For a CISO, the problem isn't a lack of tools. It's a lack of signal. Traditional scanners create thousands of alerts and send them into a backlog no one has time to clear. Leaving your team guessing at which issues actually matter to the business. Security cannot be the bottleneck. It also cannot be a liability. One overlooked trust boundary is all it takes to exfiltrate AI tokens or rack up massive API costs. Enclave provides the independent oversight required for this scale of development. We don't just scan for patterns. We follow system logic across files and services to find the architectural risks that matter. When Enclave flags an issue, it shows the context and the fix. Your team reviews the fix, approves it, and keeps shipping. Stop managing noise. Ship with confidence.
1
5
364
Enclave now has a native desktop app (macOS, Windows, Linux). If you’re doing security research and need to go local, run scripts, use your editor, and work on real files/repos without losing Enclave’s code security context, go to setting on Enclave and get started.
4
10
522
NGINX Rift is the new 18-year-old nginx RCE. Every version since 2008 in scope. We scanned 1,465 configs from 528 popular GitHub repos to see how bad it really is. What we found, and where the real attack surface actually lives 👇
2
3
28
75,521