QodoAI — agentic threat model

Not certain from the listing — The specific foundation models used are not detailed. However, as a closed-source tool, it is susceptible to proprietary model vulnerabilities, adversarial prompt injection leading to malicious code generation, and potential model reprogramming.

The agent relies heavily on codebase context and Git repository data. This introduces risks of codebase data exfiltration, context poisoning (where malicious comments or files manipulate the generator), and lack of clear data provenance for generated code.

Orchestrates code generation, testing, and reviews. A key threat is insecure tool integration, particularly if the AI-powered testing framework executes generated test code in an unsandboxed environment, or if prompt injection triggers unauthorized Git actions.

Deployed via IDE plugins and Git platform integrations. This creates a high-value target for privilege escalation, credential theft (Git tokens, IDE access), and potential lateral movement into the developer's local machine or enterprise network.

Focuses on automated code review and testing. Threats include evaluation gaming (generating code that bypasses tests but contains hidden vulnerabilities) and blind spots where the agent fails to detect complex security flaws in its own generated code.

Not certain from the listing — There is no explicit mention of compliance certifications (like SOC2, ISO 27001) or data privacy controls regarding how proprietary code sent to the platform is handled, stored, or used for training.

Integrates with Git platforms and developer ecosystems. Threats include cascading failures if the Git integration is hijacked to push malicious commits, or if the agent interacts with compromised third-party CI/CD marketplace actions.