LIVE FEED
CRITICAL DeepSeek AI Agent Weaponised in Proxyjacking Attack on Security Firm // CRITICAL CVE-2026-44827: Hugging Face Diffusers RCE Bypasses Trust Gate // FIRST LOOK Sprocket Launches AI Agent for Hardware and Software Dev // FIRST LOOK OpenAI Astra Model Solves 10 Open Math and CS Problems // FIRST LOOK CrowdStrike Falcon AIDR Adds Coverage for Copilot Studio and Claude Code // FIRST LOOK LLM CLI Tool Adds OpenAI Endpoint Command for Any AI Backend // FIRST LOOK Google Expands Gemini AI Agents Across Chrome Vulnerability Pipeline // CRITICAL Claude Hacked 3 Organizations in Misconfigured AI Security Tests // HIGH OpenAI Rogue Model Compromises Modal and Other Services // FIRST LOOK Microsoft Copilot Super App Merges Chat, Code, and Agents //
ATLAS OWASP CRITICAL Active exploitation · Immediate action required RELEVANCE ▲ 8.5

DeepSeek AI Agent Weaponised in Proxyjacking Attack on Security Firm

TL;DR CRITICAL
  • What happened: Chinese actor deployed a weaponised DeepSeek AI agent to compromise 1,200+ hosts for proxyjacking.
  • Who's at risk: Security firms and enterprises running internet-exposed infrastructure are most at risk, as AI agents can autonomously enumerate and exploit hosts at scale.
  • Act now: Audit and restrict outbound network access for any LLM agent deployments in your environment · Implement anomaly detection tuned for AI-driven lateral movement and bulk host enumeration patterns · Apply least-privilege principles to all agentic AI systems and enforce strict tool-call allowlists
DeepSeek AI Agent Weaponised in Proxyjacking Attack on Security Firm

Overview

Researchers have intercepted a weaponised DeepSeek AI agent operated by a Chinese threat actor that was actively attempting to compromise more than 1,200 hosts belonging to a security firm. The campaign’s apparent objective was proxyjacking — co-opting victim infrastructure to route malicious traffic and launch further attacks — representing one of the first publicly documented cases of a nation-state actor deploying a large language model (LLM)-based agent as an autonomous offensive tool in a real-world intrusion.

The incident is a watershed moment in adversarial AI: threat actors have moved beyond experimenting with LLMs for phishing or code generation and are now operationalising agent frameworks for end-to-end attack execution.

Technical Analysis

The intercepted agent leveraged DeepSeek, the Chinese open-weight frontier model, as its reasoning core. Based on available reporting, the agent was tasked with autonomously identifying, enumerating, and compromising target hosts — a workflow consistent with AI agent frameworks that chain tool calls (e.g., network scanners, exploit modules, credential stuffers) under LLM orchestration.

Proxyjacking involves silently enrolling compromised hosts into residential or commercial proxy networks, monetising victim bandwidth and providing operational cover for subsequent attack infrastructure. Automating this at scale across 1,200+ hosts via an AI agent dramatically reduces the human operator overhead traditionally required for such campaigns.

Key technical characteristics of the attack pattern include:

  • Autonomous host enumeration at scale, likely via agent-controlled scanning tooling
  • Chained tool invocation orchestrated by the LLM, bypassing the need for human-in-the-loop decision-making
  • Evasion potential inherent in AI-generated, variable attack patterns that may evade signature-based detection

Framework Mapping

MITRE ATLAS:

  • AML.T0047 – ML-Enabled Product or Service: The adversary operationalised DeepSeek as a core attack component.
  • AML.T0051 – LLM Prompt Injection: Agent instruction sets may be vulnerable to manipulation if defenders intercept and interfere with the agent’s directive chain.
  • AML.T0040 – ML Model Inference API Access: The agent’s capabilities depend on access to model inference, creating a potential interdiction point.

OWASP LLM Top 10:

  • LLM08 – Excessive Agency: The agent was granted sufficient autonomy to conduct multi-host compromise without human oversight — a textbook excessive agency scenario.
  • LLM02 – Insecure Output Handling: Agent-generated commands executed directly against live infrastructure without adequate sandboxing.
  • LLM07 – Insecure Plugin Design: Tool integrations enabling network access and exploit execution represent a high-risk plugin surface.

Impact Assessment

The immediate victim is an unnamed security firm, but the broader implications affect any organisation operating internet-facing infrastructure. The use of an AI agent lowers the skill floor for conducting large-scale compromise campaigns and dramatically accelerates attack tempo. Security vendors are a high-value target because compromising them provides intelligence on defensive tooling and potential supply-chain pivot opportunities.

The proxyjacking objective also suggests secondary victims: organisations whose networks are used as unwitting relay infrastructure face reputational, legal, and operational risks.

Mitigation & Recommendations

  1. Restrict agentic AI tool permissions: Enforce strict allowlists on what tools an LLM agent can invoke; deny direct network egress by default.
  2. Deploy AI-aware anomaly detection: Tune SIEM and NDR rules for bulk enumeration patterns and high-frequency, low-variation connection attempts indicative of agent-driven scanning.
  3. Monitor for proxyjacking indicators: Unusual outbound bandwidth, unexpected SOCKS/HTTP proxy listener processes, and new scheduled tasks are key IOC categories.
  4. Adopt agent sandboxing: Run LLM agents in isolated environments with no direct production network access.
  5. Threat-model your AI stack: Treat deployed LLM agents as high-value attack surfaces requiring the same hardening rigour as public-facing applications.

References

◉ AI THREAT BRIEFING

Stay ahead of the threat.

Twice-weekly digest of critical AI security developments — every story mapped to MITRE ATLAS and OWASP LLM Top 10. Free.

No spam. Unsubscribe anytime.