BoletimSec•September 1, 2026•🇵🇹Translated from Portuguese

Secure AI-Assisted Development: Five Critical Practices for Vibe Coding

Developing with AI has become the natural route to move an idea from concept to working code quickly. The problem is that most flaws in applications created this way do not originate from an error in the model but from an assumption made by the developer. The AI delivers exactly what was requested, and security is almost never part of that request.

Five points concentrate the majority of problems. Developers are advised to describe what the application must not do. Prompts usually detail functionality while ignoring restrictions. The AI implements the happy path with precision but does not imagine a malicious user on its own. When requesting a feature, teams should also specify who cannot access it, which values are invalid, and what must happen when someone attempts to bypass the flow. An undeclared restriction is a non-existent restriction.

Authentication and authorization are not the same. The AI implements login without difficulty, which is precisely where the trap lies. Authentication confirms who the user is; authorization defines what that user may access. Without explicit instruction, applications commonly verify only that someone is logged in and fail to check whether the record belongs to that user. Changing a number in the URL and viewing another client’s data remains the most frequently observed flaw in newly built applications.

Teams must review every dependency the AI selects. Each suggested library enters the project carrying its own history of vulnerabilities. Models tend to recommend packages that appear frequently in training data, which does not guarantee they are actively maintained or updated. Checking the last update date of each dependency and running an automated scan before release is recommended, because an inherited flaw is as exploitable as one written by the developer.

A secret removed from code does not disappear from the repository. An API key remains in commit history and stays accessible to anyone with repository access, as well as to automated scans that target public repositories. When a credential leaks, the only safe action is to revoke it and generate a new one rather than editing the file.

Business logic is the blind spot. No model knows the rules of a specific business. The AI does not understand that a coupon cannot be applied twice, that a balance should not accept a negative value, or that a cancelled order cannot generate repeated refunds. These flaws pass every automated scan because the code is technically correct. Only someone who understands the business flow can identify them.

Applications developed with AI have already entered the sights of cybercriminals, mainly because they repeat flaws that can be identified and exploited at scale. In addition to good practices during development, submitting the application to a pentest before production is advised. In this scenario, the HackerSec Pentest Platform has become an alternative used by developers and vibe coders seeking to test the cybersecurity of their applications with quality, agility, and a more accessible model. Rapid development is part of this new way of creating software.

Related articles

Habr•AI Security

AI Agents Exploit PaperCut Flaw, Compromising 395 Organizations Across 48 Countries

PaperCut released a security bulletin on 27 August 2026. GreyNoise observed the first real-world code execution just four days later, with the operator moving from initial access to execution in under four hours. After the mass campaign launched, 11 organizations were compromised in only 26 seconds. In total, at least 440 PaperCut NG/MF instances belonging to 395 organizations were breached. The incident is detailed in the November report by Google Threat Intelligence Group and Mandiant, which examines the role of AI agents in the attacks. GTIG also discovered an automated exploit_agent system capable of handling exploitation without constant human input. Additional cases involved LLMjacking and unauthorized configuration changes in Claude Code repositories at cryptocurrency firms.

安全客•AI Security

Google Threat Intelligence Group Warns of Fully Autonomous AI Cyberattacks Within Six Months

Google's Threat Intelligence Group (GTIG) has observed the first real-world instances of attackers using multi-agent AI frameworks to autonomously discover vulnerabilities, generate exploits, and compromise targets without human intervention. The discovery came from an exposed server running a framework called exploit_agent that analyzed software update logs from popular web applications to identify and exploit weaknesses. Four previously defensive tools—ARTEX, CAIRN, CyberStrikeAI, and HexStrike AI—have been repurposed for offensive operations, with documented cases targeting French media, U.S. aerospace, and cryptocurrency firms. GTIG projects that low-complexity automated attacks will become common within three months, while sophisticated fully autonomous operations are expected within six months. The report highlights how these systems compress patch windows, overwhelm security teams with AI-generated proof-of-concepts, and turn detailed vendor advisories into attack playbooks. Defenders are urged to minimize public exposure, accelerate patching cycles to weekly, and tightly control API keys to prevent LLMjacking.

Habr•AI Security

OpenAI Rolls Out KYC, Hardware Keys and Tiered Access for Cybersecurity Tasks in GPT-6.2

OpenAI has introduced stricter access controls for GPT-6.2 Astra and Sol models when users attempt cybersecurity-related tasks. Certain legitimate security research and testing activities now trigger automatic blocks unless the user obtains Daybreak trusted access. The program requires paid subscriptions, FIDO2 hardware keys, Advanced Account Security, and identity verification through Persona. Developers report that even after meeting preliminary requirements, access to reduced refusal rates is not guaranteed and may require separate organizational approval. The changes stem from the models reaching Critical capability levels under OpenAI’s Preparedness Framework for dual-use cybersecurity skills. Similar verification processes previously led to account blocks for users of competing services such as Anthropic’s Claude.

AntiMalware•AI Security

Positive Technologies Releases PT Application Inspector Plugins 3.0.0 with AI Agent Support via Model Context Protocol

Positive Technologies has launched version 3.0.0 of its free PT Application Inspector plugins, introducing native support for AI agents through an integrated MCP server. The update enables AI agents to initiate vulnerability scans on entire projects or specific code changes, review findings, and assist developers in remediation directly within supported environments. Integration via the Model Context Protocol connects tools such as OpenCode, Claude Code, and Codex, providing agents with detailed vulnerability data including exploitation conditions. Static analysis remains the core detection method, while the new AI Hooks feature automatically validates modifications made by agents without requiring full project rescans. The How to Fix capability, which generates AI-driven remediation suggestions, is now available in Visual Studio Code in addition to JetBrains IDEs, with support for on-premise models to keep source code internal. Director of AppSec and WAF Products Anton Zhabolenko stated the goal is to embed vulnerability detection and fixing into the code generation workflow itself.