EN PT-BR
← Voltar ao feed
high managed service providers technology

Threat actors use ARTEX agentic AI framework to harvest secrets from public GitHub repos and pivot into Entra ID tenants

1 fonte(s) · 1 atualização(ões) · publicado 06/11/2026 12:57 · coletado há 1 hora

Baseado só no resumo do feed. O site da fonte não liberou o texto completo para o Tifon, então esta análise saiu apenas do resumo publicado no feed e pode estar incompleta. Ela é atualizada quando outra fonte cobrir o assunto. Ler na fonte original ↗

Microsoft Threat Intelligence reported on 5 November 2026 that threat actors are using the agentic offensive security framework ARTEX and similar AI tooling to mass-query public GitHub repositories for exposed credentials, OAuth application secrets and AI inference API keys, then automatically abuse them against the victim's cloud tenant. The activity began in August 2026, with the AI framework submitting large volumes of GitHub queries combining a target organization's name with keywords for secrets, cloud services or AI providers (microsoft.com). Stolen Entra ID application credentials were then used to sign into Microsoft 365 and Azure environments, including at managed service providers, with at least one case of a vendor-owned multitenant application compromised at the source and reused across downstream tenants (microsoft.com). Microsoft observed an AI agent progress from scanning GitHub for secrets to exfiltrating data from Azure Key Vault in just five minutes (microsoft.com). The article notes attribution for the GitHub scanning is not established, while ARTEX was previously tied to a China-nexus actor abusing ConnectWise Cloud Backup; Microsoft's earlier reporting names that activity Storm-0940 (microsoft.com).

Detalhes técnicos

As early as 28 October 2026, Microsoft observed successful service principal sign-ins from 199.19.77[.]84 involving multiple application IDs across impacted customers, used for cloud resource discovery and credential and data exfiltration from Azure Key Vaults and Storage Accounts, plus abuse of Azure AI services (microsoft.com). Sign-ins also came from 199.19.77[.]18, a Tor exit node; reconnaissance against victim Azure AI workloads came from 157.22.126[.]128, and operations from 65.87.223[.]26 included shell commands embedded in a user agent and attempts to obtain App Service authentication tokens (microsoft.com). The actor targeted operations returning storage account keys, App Service settings, connection strings and publishing credentials, AI/ML connections and datastores and AKS user credentials, then accessed SharePoint and OneDrive content, downloaded files, read mailbox items and issued Microsoft Graph search requests (microsoft.com). ARM telemetry showed adaptive behaviour: failed HTTP 400 responses were followed within tens of seconds by retries with corrected API versions or HTTP methods returning 200 (microsoft.com). Agents also obtained tokens for single-tenant OAuth applications, searched Azure DevOps for further secrets and used Run Command to execute scripts on Azure VMs (microsoft.com). Todyl reported a similar campaign involving the same IP addresses (microsoft.com).

Remediação

Organizations should scan their GitHub code for secrets, remove them and immediately rotate any exposed keys or credentials, treating any secret found in a public repository and its associated application as compromised; removing the original commit alone does not remediate the exposure (microsoft.com). Microsoft recommends enabling GitHub secret scanning and public monitoring, push protection, GitHub Advanced Security / Secret Protection for Azure DevOps, enforcing least privilege on workload identities, enabling Defender for Cloud protections and migrating OAuth applications from client secrets to managed identities (microsoft.com). Defenders should hunt for service principal sign-ins from the listed IP addresses and for unexpected Key Vault, Storage, Graph and Run Command activity by application identities.

Linha do tempo

  1. cybersecuritydive.com ↗ · pub. 06/11/2026 12:57 · coletado 06/11 14:00 primeiro registro só resumo do feed

    Threat actors use ARTEX agentic AI framework to harvest secrets from public GitHub repos and pivot into Entra ID tenants

    ler a análise desta fonte

    Microsoft Threat Intelligence reported on 5 November 2026 that threat actors are using the agentic offensive security framework ARTEX and similar AI tooling to mass-query public GitHub repositories for exposed credentials, OAuth application secrets and AI inference API keys, then automatically abuse them against the victim's cloud tenant. The activity began in August 2026, with the AI framework submitting large volumes of GitHub queries combining a target organization's name with keywords for secrets, cloud services or AI providers (microsoft.com). Stolen Entra ID application credentials were then used to sign into Microsoft 365 and Azure environments, including at managed service providers, with at least one case of a vendor-owned multitenant application compromised at the source and reused across downstream tenants (microsoft.com). Microsoft observed an AI agent progress from scanning GitHub for secrets to exfiltrating data from Azure Key Vault in just five minutes (microsoft.com). The article notes attribution for the GitHub scanning is not established, while ARTEX was previously tied to a China-nexus actor abusing ConnectWise Cloud Backup; Microsoft's earlier reporting names that activity Storm-0940 (microsoft.com).

    Technical Details

    As early as 28 October 2026, Microsoft observed successful service principal sign-ins from 199.19.77[.]84 involving multiple application IDs across impacted customers, used for cloud resource discovery and credential and data exfiltration from Azure Key Vaults and Storage Accounts, plus abuse of Azure AI services (microsoft.com). Sign-ins also came from 199.19.77[.]18, a Tor exit node; reconnaissance against victim Azure AI workloads came from 157.22.126[.]128, and operations from 65.87.223[.]26 included shell commands embedded in a user agent and attempts to obtain App Service authentication tokens (microsoft.com). The actor targeted operations returning storage account keys, App Service settings, connection strings and publishing credentials, AI/ML connections and datastores and AKS user credentials, then accessed SharePoint and OneDrive content, downloaded files, read mailbox items and issued Microsoft Graph search requests (microsoft.com). ARM telemetry showed adaptive behaviour: failed HTTP 400 responses were followed within tens of seconds by retries with corrected API versions or HTTP methods returning 200 (microsoft.com). Agents also obtained tokens for single-tenant OAuth applications, searched Azure DevOps for further secrets and used Run Command to execute scripts on Azure VMs (microsoft.com). Todyl reported a similar campaign involving the same IP addresses (microsoft.com).

    Remediation

    Organizations should scan their GitHub code for secrets, remove them and immediately rotate any exposed keys or credentials, treating any secret found in a public repository and its associated application as compromised; removing the original commit alone does not remediate the exposure (microsoft.com). Microsoft recommends enabling GitHub secret scanning and public monitoring, push protection, GitHub Advanced Security / Secret Protection for Azure DevOps, enforcing least privilege on workload identities, enabling Defender for Cloud protections and migrating OAuth applications from client secrets to managed identities (microsoft.com). Defenders should hunt for service principal sign-ins from the listed IP addresses and for unexpected Key Vault, Storage, Graph and Run Command activity by application identities.