Hunt.io Exposes Suspected Chinese Cyber Espionage Operation Using Agentic LLMs Claude Code and DeepSeek
In July 2026 Hunt.io published research on a suspected Chinese cyber espionage campaign uncovered through an exposed directory on a Hong Kong server. The leak contained 2,431 files including victim source code, operation logs, web shells, exploitation scripts, scan results and phishing page clones.
The most unusual element of the report is evidence of Claude Code and DeepSeek-v4-pro operating together. Researchers concluded that Claude Code performed agentic tasks and preserved session context while DeepSeek handled reasoning, script refinement and selection of the next operational step. The findings do not implicate the model vendors themselves; they only demonstrate operator use of the products or interfaces.
Infrastructure cluster and TencShell
The investigation began with the known TencShell C2 cluster. Analysts searched for servers sharing an identical SHA-256 hash in HTTP headers on port 1111 and located 13 IP addresses across four autonomous systems. Several hosts also reused SSH host keys and TLS certificates, strengthening cluster linkage without proving single ownership.
One server at 112.213.124[.]132 exposed multiple services: port 1111 for HTTP delivery of malicious binaries, port 3000 running DeepAudit for source-code auditing, port 5003 running ARL for asset reconnaissance, port 8084 running Vshell C2, and port 8888 serving an open directory of operational data.
Attack chain and initial access
Operators employed several initial-access vectors rather than a single exploit. Reconnaissance scripts performed DNS brute force, certificate transparency lookups, adjacent IP discovery and HTTP fingerprinting. Priority targets included VPN gateways, GitLab, Jira, webmail and cloud services. More than 5,890 government hosts across ten countries were scanned and scored.
Documented compromises include SQL injection against a Taiwanese chemical company that yielded database contents and development-environment source code; exposure of Supabase anon keys and Azure Logic Apps SAS tokens at a Taiwanese telecom and edge-equipment manufacturer; and SQL injection via SQLMap against a Thai government administrative service that led to an administrative panel and a GIF-polyglot web shell.
In an Afghan Laravel 5.8.38 application, operators obtained source code, encryption keys, database credentials and mail-handling components, then built a Python script exploiting Laravel deserialization for remote code execution.
AI agent workflow
Logs revealed persistent Claude Code 2.1.165 sessions between 8 and 12 June 2026. The operator defined objectives and approved high-risk moves, Claude Code managed tools, shell commands, session state and parallel tasks, while DeepSeek-v4-pro performed analysis, bypass logic and script generation. The architecture reduces the cost of repetitive actions such as result aggregation, configuration review and context transfer between operator shifts.
A parallel disclosure by Anthropic described campaign GTG-1002, attributed with high confidence to a Chinese state group. Operators used prompt fragmentation and a cover story of authorized security testing to direct Claude Code, which performed 80–90 percent of tactical work while humans retained control over target selection and data exfiltration volume.
Defensive recommendations
Organizations should close public access to repositories, archives, backups and administrative interfaces; scan continuously for exposed secrets in client-side JavaScript; remediate SQL injection with parameterized queries; audit Laravel and other framework applications for outdated versions and unsafe deserialization; and detect web shells by MIME type and anomalous GET parameters rather than file extension alone.
Related articles
Thousands of Grok-Generated Apps Expose Sensitive Corporate Data Through Default Public Access
Security firm Claroc scanned 43,551 Grok-built application addresses and found 37,571 still online, with 94.7 percent requiring no login. Approximately 650 to 800 of these apps contained sensitive internal data belonging to SpaceX, X, Tesla, and 30 other organizations, including six Fortune 500 companies. Exposed records included ICU patient reports with lab results and ventilator status, contractor timesheets containing plaintext passwords, and Tesla service-center performance evaluations listing employee names, efficiency metrics, and bonuses. Researchers demonstrated that Grok sometimes inverts permission-check logic, allowing unauthorized Google accounts to view and modify data after login. In contrast, ChatGPT-generated apps default to private settings, preventing access even when URLs are discovered via passive DNS. The incident highlights how AI coding tools lower the barrier to publishing internal applications while weakening the review processes that traditionally protected sensitive data.
Enterprise Security Requirements Push Russian Developer to Deploy 125B MoE LLM Locally on Consumer Hardware
A cybersecurity journalist and platform developer detailed his transition from cloud-based AI agents to a fully local 125B-parameter MoE model after enterprise clients raised strict data-exfiltration concerns. The move was driven by the need to keep task statements, source code, configuration files, logs, and regulated personal data inside the corporate perimeter. After testing multiple inference engines, he settled on the Strata engine running a Qwen3.8-Flash-Next model quantized to IQ3_S, achieving 22-25 tokens per second generation and over 500 tokens per second prefill on an RTX 5060 Ti 16 GB GPU paired with a Xeon E5-2640 v3 and 128 GB DDR4. Extensive calibration of expert caching, PCIe fraction, KV streaming, and speculative decoding proved critical to reaching production-grade performance. The resulting setup now handles real agentic workloads such as incident investigation from traces, backlog grooming, and code generation without any data leaving the workstation. The author concludes that hybrid cloud-local workflows will become standard for development teams handling sensitive information within the next one to two years.
VK Tech Releases Offline-Capable VK AI Space 26.3 for Secure Enterprise AI Agents
VK Tech has launched version 26.3 of its corporate AI platform VK AI Space, enabling organizations to deploy generative AI agents that operate entirely without internet access. The update integrates seven modules for model connectivity, knowledge base management, and multi-agent orchestration while supporting full on-premises installation on customer hardware. Key security controls include role-based access management, usage quotas, comprehensive audit logging, and configurable checkpoints that pause agent actions for human approval when required. Agents can interact with internal APIs, databases, and file systems through multi-step workflows, with built-in validation against test datasets and restrictions on tool usage. The platform also provides multi-level memory, ready-to-use component libraries, and hooks for fine-tuning agent behavior. VK Tech confirmed that version 26.3 successfully passed testing under an approved program that specifically verified operation in air-gapped environments.
AI Coding Assistants Generate Insecure Code and Amplify Supply-Chain Risks in Production
A detailed analysis of AI coding assistants reveals that generated code contains vulnerabilities in 45% of cases according to Veracode research, with models frequently choosing unsafe options for log injection and XSS. Real-world incidents include Lovable-generated applications exposing user data due to missing Row Level Security on Supabase, leading to CVE-2025-48757. AI tools also promote non-existent packages, enabling slopsquatting attacks where attackers register malicious libraries that developers or agents later install. Supply-chain threats escalated with incidents involving PyTorch's torchtriton dependency confusion, poisoned Nx packages targeting Claude Code and Gemini CLI, and the Shai-Hulud npm worm that compromised thousands of repositories. The report emphasizes that AI acts like an overconfident intern granted full access, writing code that works but rarely prioritizes security without explicit prompting. Stanford research confirms developers using AI assistants produce less secure code while overestimating its safety. Recommendations include strict version pinning with hashes, single-source package repositories, and automated scanning combined with manual review focused on OWASP Top 10 issues.