AML.T0095.000
Code Repositories

MITRE source definition

Adversaries may search public code repositories for information about a victim or victim system that can be used during targeting. Victims may store code or artifacts related to their AI systems in repositories on various third-party websites such as GitHub, GitLab, SourceForge, and BitBucket. Adversaries may search code repositories of common AI tools, frameworks, models, or agentic systems that are used--but not owned--by the victim.

Public code repositories can often be a source of various information about victims, such as commonly used AI frameworks, libraries, models, datasets, agents, and agent tools, as well as the names of employees. Adversaries may also identify more sensitive data, including accidentally leaked credentials or API keys (ex: [Credentials from AI Agent Configuration](/techniques/AML.T0083)). Information from these sources may reveal opportunities for other forms of Reconnaissance (ex: [Gather RAG-Indexed Targets](/techniques/AML.T0064)), establishing operational resources (ex: [Acquire Public AI Artifacts](/techniques/AML.T0002)), Discovery (ex: [Discover AI Agent Configuration](/techniques/AML.T0084)) and/or Initial Access (ex: [Valid Accounts](/techniques/AML.T0012) or [Phishing](/techniques/AML.T0052)).

Source modified 2026-05-27. Reproduced from the pinned ATLAS release; inline technique links resolve to local reference pages.

Parent, sub-techniques and ATT&CK references

• AML.T0095 Search Open Websites/Domains — parent
• T1593.003 Code Repositories — explicit ATLAS ATT&CK reference

Source-backed defensive context

MITRE mitigations

• AML.M0039 AI Honeypots

MITRE case studies

• AML.CS0051 OpenClaw Command & Control via Prompt Injection · Exercise
• AML.CS0067 Claude Code GitHub Action Secret Exposure · Exercise
• AML.CS0070 Threat Actor Uses a DeepSeek-Powered Hermes Agent in Langflow and n8n Exploitation Attempts · Incident

These are explicit source relationships, not independently reproduced incidents or validated detection coverage.

Simulation and telemetry boundary

This is a technique reference page, not a runnable simulation. No ATLAS-specific telemetry mapping, local attack execution or detector validation is asserted. MITRE maturity describes its source evidence, not a 1200km lab result.

For broader context—not technique-specific control mappings—see AI Security, AI Security Course, and detection-validation methodology.

Provenance and attribution

Immutable MITRE ATLAS source · Import provenance · Attribution and transformation notice · Apache License 2.0

Copyright 2021-2026 MITRE. Source text and explicit relationships are retained; navigation, formatting and local links are provided by 1200km.

No explicit relationship in this pinned source.