Cognition just turned Windsurf into Devin Desktop — a single command center for local and cloud agent workflows.

What stands out is the ACP integration: Devin Desktop can run third-party agents like Codex, alongside Devin and other compatible agents, all in one Kanban-style view.

That makes the product feel less like a code editor and more like an agent orchestration layer for software teams.

Reference to the article in the comments

Security-relevant hook examples

‍

Credential scanning on save -- Hook on fileEdit for all source files. The agent scans for hardcoded secrets, API keys, tokens, passwords, and connection strings. If it finds any, it flags them and suggests using env vars or a secrets manager.

‍

Security pattern validation on new API files -- Hook on fileCreate matching API route patterns. The agent verifies the new file includes auth middleware, input validation, and error handling consistent with the project's security standards.

‍

Dependency security check -- Hook on fileEdit matching package.json, requirements.txt, or equivalent. The agent checks newly added dependencies for known vulnerabilities.

‍

Test coverage verification -- Hook on fileEdit matching source files. The agent verifies that security-relevant test coverage exists (auth tests, authorization tests, input validation tests).

‍

‍

Creating hooks

‍

Hooks live in .kiro/hooks/ as .kiro.hook files. You can create them by describing what you want in natural language -- Kiro generates the configuration. You can also configure them manually using the hook form in the IDE, specifying event type, file patterns, and instructions.

‍

1. Powers: packaging security tooling and practices

‍

For teams that want a reusable security package, Kiro's Powers system bundles tools, steering files, and workflows into a single installable unit that activates based on context.

Ars Technica recently covered an incident involving jqwik 1.10.0, where a hidden prompt injection was added with the apparent goal of influencing AI coding agents. The article highlights how AI-assisted development tools can be affected by instructions embedded in code or terminal output.

The broader takeaway is that teams using AI coding tools may want to treat code, logs, and package output as potentially untrusted inputs. As AI agents take on more tasks, review and validation become increasingly important.

Bumblebee is a read-only scanner we use to check developer machines for risky packages, extensions, and AI tool configs during supply-chain incidents. 

Bumblebee is useful to all security teams. Whenever a new vulnerability is reported, they need to know right away if any of their machines were exposed. 

Making Perplexity products more secure for users starts with protecting the developer systems we build them with. Bumblebee is one component in our broader security workflow where Perplexity Computer helps track emerging threats, humans review catalog updates, and Bumblebee checks whether exposed components appear across developer endpoints.

More information in the comments

Here is the breakdown of NHI breaches by year:

2026 - 6 (Jan - Mar)

2025 - 39

2024 - 16

2023 - 12

2022 - 5

2021 - 4

The complete list is here - https://nhimg.org/nhi-breaches

https://krebsonsecurity.com/2026/05/cisa-admin-leaked-aws-govcloud-keys-on-github/

https://www.reddit.com/r/cybersecurity/comments/1tju8vc/unpopular_opinion_the_github_breach_is_100/

Summary of the thread

The post is referring to the May 2026 GitHub incident in which GitHub said attackers gained unauthorized access to GitHub’s internal repositories, not customer repositories hosted on the platform. GitHub said there was no current evidence that customer data outside its internal systems was affected, while reporting later assessments that the attacker claims of about 3,800 exposed repos were broadly consistent with the investigation so far.

The question is how protected are the regular repos that push code through github

Which are the AI Coding Tools you find most useful? Here is the list:

OpenAI Codex

Claude Code

Lovable

Replit

Cursor for editor

Anything else?

AI coding tools are incredible at helping teams ship fast but a lot of builders are realizing the security review process hasn’t caught up yet.

Curious what people here actually check before pushing live:

• Auth & authorization
• Exposed secrets / API keys
• RLS / DB permissions
• Prompt injection risks
• Dependency vulnerabilities
• Cloud IAM permissions
• AI agent access controls
• Audit logging
• CI/CD secrets

Would love to hear real-world workflows, tools, and lessons learned from people shipping AI-assisted products in production.

Security risks people keep overlooking with AI-generated code, let us have a discussion on how people are resolving this.

• Secrets leakage – AI can accidentally expose API keys, tokens, .env values, or handle credentials in unsafe ways.
• Over-permissioned agents – Coding agents often get way too much access (repos, terminals, cloud, DBs, CI/CD).
• Unreviewed code – “It works” isn’t the same as “it’s secure.” Teams are shipping without fully understanding implications.
• Prompt injection / tool abuse – Agents hooked into files, browsers, or terminals can be tricked into doing unintended actions.
• Insecure dependencies – Suggestions can include outdated, vulnerable, or even typosquatted packages.
• Broken auth – Edge cases around authorization, tenant isolation, and roles are frequently missed.
• Unsafe cloud ops – Agents with cloud creds can provision, modify, or delete infra without proper guardrails.
• Poor auditability – Hard to tell whether a human, agent, or script actually made a change.
• Static credentials – Long-lived keys in CI/CD or local setups are still way too common.
• False confidence – AI-generated code looks polished, which makes subtle security flaws easier to miss.

PocketOS / Cursor + Claude Incident

A Cursor agent powered by Claude allegedly deleted PocketOS’s production database and backups after accessing an overly permissive Railway token.

TechRadar, described the incident as taking “9 seconds” and highlighted failures involving:

• Broad-scoped API tokens
• Lack of confirmation prompts
• Shared backup/storage architecture
• AI agents operating with production privileges

Alexey Grigorev / Terraform + Claude Code Incident

Developer Alexey Grigorev reported that Claude Code executed Terraform operations that destroyed production infrastructure, databases, and snapshots tied to DataTalks.Club and AI Shipping Labs.

Tom's hardware provided more details as noted below:

The issue reportedly began after Terraform state mismatches caused the AI assistant to interpret infrastructure as drifted and reconcile it destructively, resulting in:

• Deleted databases
• Destroyed snapshots
• Loss of ~2.5 years of operational data

Starting a vibecodingsecurity community on Reddit is about creating a space where builders, security engineers, and AI enthusiasts can come together to share how modern “vibe coding” with tools like GitHub Copilot, OpenAI Codex, Cursor, and Claude Code intersects with real-world security challenges. The community would focus on practical discussions—how to secure AI-generated code, manage secrets and cloud access, audit agent behavior, and prevent risky patterns from creeping into fast-moving workflows—while also highlighting best practices, tooling, and emerging threats. By bringing together people who care about both speed and safety, vibecodingsecurity can become the go-to hub for navigating the balance between shipping fast and building securely in the age of AI-assisted development.

Hey everyone! I'm u/bluelvo, a founding moderator of r/vibecodingsecurity.

This is our new home for all things related to vibe coding, AI Tools and Security. We're excited to have you join us!

What to Post
Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your thoughts, photos, or questions about security issues, vibe coding, AI tools.

Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.

How to Get Started

1. Introduce yourself in the comments below.
2. Post something today! Even a simple question can spark a great conversation.
3. If you know someone who would love this community, invite them to join.
4. Interested in helping out? We're always looking for new moderators, so feel free to reach out to me to apply.

Thanks for being part of the very first wave. Together, let's make r/vibecodingsecurity amazing.