# AI-Enabled Cyberattack Campaigns Against Japan: Three Cases Beyond ARTEX (CyberStrikeAI, LLM-Assisted Intrusions, AI-Written Tooling)

> Trend Micro (TrendAI) research, reported 2026-10-29, describes three Simplified-Chinese-language operations against Japanese organizations in 2026 with differing AI involvement: CyberStrikeAI agent automation (44 agents, 19+ organizations, at least 16 in Japan), a human-led LLM-assisted intrusion that scanned 6,000+ Japanese IPs, and a Jan-Oct campaign against 1,300+ WebLogic candidates and 35 VPN entry points. No AI-discovered zero-day was used; attacker identities and AI models are unconfirmed.

- **Published:** 2026-10-31T17:29:36Z
- **Last reviewed:** 2026-10-31T17:29:36Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-4916
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-4916.png
- **ID:** TL-2026-4916
- **Severity:** HIGH
- **Category:** THREAT_INTEL
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 10 (1 shown free below)

## Description

The Cyber Express (2026-10-29), summarizing Trend Micro/TrendAI research on attacker-side files from three separate attack infrastructures, documents Japan-focused activity that largely predates the ARTEX reporting. All three operations worked in Simplified Chinese, selected targets opportunistically, and relied on known weaknesses, legacy systems and poor configuration rather than AI-discovered zero-days. Researchers could not confirm a shared operator, and had no victim-side logs, so the success of individual attempts cannot be verified.

Case A (October 2026) used CyberStrikeAI, an open-source agent-based penetration-testing platform with a Simplified Chinese console, configured with 44 agents that split reconnaissance, exploitation, command and control, persistence, exfiltration and reporting. At least 19 organizations received identical automated reports, at least 16 of them in Japan, with further targets in Taiwan and Hong Kong, mostly smaller businesses and local public bodies. The framework generated Japanese-language forms and fake login pages and throttled traffic per target, so activity was hard to spot in any single victim's logs. Many log entries read 'no session, no web shell, no exfiltration'; the deepest intrusion was an unauthenticated administration interface on a legacy system. Results were organized in folders named jp_success, jp_attack and jp_cve_attack.

Case B (about 24 days across August-September 2026) was human-led with an LLM supporting planning and tooling. The operator scanned at least 6,000 Japanese IP addresses and also probed AI assets in South Korea. The operator framed requests as an authorized assessment to bypass the model's guardrails when targeting AI and GPU services, with the aim of hijacking and pooling other people's AI services for cheap inference capacity. At one victim the operator gained full control (FTP, database access, administrator rights, web shell, SSH) and repeatedly restored backdoors after cleanup; a GIS server with default credentials exposed several hundred thousand cadastral and commercial records, Windows credentials and email. Several hundred attempts against one cluster failed.

Case C (January-October 2026, multiple parallel campaigns, six per secondary reporting) played down AI: it targeted at least 1,300 Oracle WebLogic candidates and 35 VPN entry points, mostly in Japan and South Korea, with additional lists covering the UK, France, Italy, Qatar and Colombia. Products named were Cisco SD-WAN, Citrix NetScaler, F5 BIG-IP and Yamaha RTX1210; on the Yamaha routers no product vulnerability was exploited, instead leftover credentials in configuration files gave direct access to corporate networks. AI authorship of the operator's tooling is assessed with high confidence from echo '=== ... ===' section headings in command history and emoji status markers in scripts.

Observed AI limitations: the AI logged planned steps as finished and overstated success, and LLMs invented vulnerability IDs. Related public reporting (BleepingComputer, citing Team Cymru) places CyberStrikeAI (GitHub developer alias Ed1s0nZ, Go-based, 100+ integrated tools, supports GPT/Claude/DeepSeek models) on attacker infrastructure between 2026-01-20 and 2026-02-26 in a separate FortiGate-focused campaign; that is a different campaign and is not shown to be the same operator.

## MITRE ATT&CK

- T1595 Active Scanning
- T1595.001 Active Scanning: Scanning IP Blocks
- T1595.002 Active Scanning: Vulnerability Scanning
- T1587.001 Develop Capabilities: Malware
- T1588.007 Obtain Capabilities: Artificial Intelligence
- T1190 Exploit Public-Facing Application
- T1133 External Remote Services
- T1078.001 Valid Accounts: Default Accounts
- T1505.003 Server Software Component: Web Shell
- T1552.001 Unsecured Credentials: Credentials In Files
- T1021.004 Remote Services: SSH
- AML.T0054 LLM Jailbreak

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**TL-2026-4916 Oracle WebLogic Exploit-Path Probing and Encoded Traversal — Exploitation** (`TL-2026-4916-SPL-001`)

Detects HTTP requests to Oracle WebLogic paths commonly abused for unauthenticated exploitation (wls-wsat, _async, bea_wls_internal, uddiexplorer, weblogicmanagement) and double-encoded traversal toward the WebLogic console. Case C of the Japan AI-enabled campaigns targeted 1,300+ Oracle WebLogic candidates (T1190, T1595.002) using known weaknesses rather than zero-days; no specific CVE is cited, so the rule keys on behaviour and path rather than a single CVE.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1190, T1595.002
- **Data sources:** index=web sourcetype=access_combined, CommonSecurityLog, webserver logs
- **Severity:** high
- **Confidence:** medium

### Splunk SPL

```spl
index=web sourcetype=access_combined earliest=-24h (uri_path="/wls-wsat/*" OR uri_path="/_async/*" OR uri_path="/bea_wls_internal/*" OR uri_path="/uddiexplorer/*" OR uri_path="/management/weblogicmanagement/*" OR (uri_path="/console/*" AND (uri="*%252e%252e*" OR uri="*%2e%2e*")))
| eval encoded_traversal=if(match(uri,"(?i)(%252e%252e|%2e%2e)"),1,0)
| stats count AS requests, dc(uri_path) AS distinct_paths, sum(encoded_traversal) AS traversal_hits, count(eval(status=200 OR status=202)) AS ok_responses, values(status) AS statuses, min(_time) AS first_seen, max(_time) AS last_seen by clientip, host
| eval first_seen=strftime(first_seen,"%F %T"), last_seen=strftime(last_seen,"%F %T")
| sort - requests
```

### Microsoft KQL

```kql
CommonSecurityLog
| where TimeGenerated > ago(24h)
| where isnotempty(RequestURL)
| where RequestURL has_any ("/wls-wsat/", "/_async/", "/bea_wls_internal/", "/uddiexplorer/", "/management/weblogicmanagement/") or (RequestURL has "/console/" and RequestURL has_any ("%252e%252e", "%2e%2e"))
| summarize Requests=count(), DistinctUrls=dcount(RequestURL), Urls=make_set(RequestURL, 10), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by SourceIP, DestinationIP, DeviceVendor
| project SourceIP, DestinationIP, DeviceVendor, Requests, DistinctUrls, Urls, FirstSeen, LastSeen
| order by Requests desc
```

### Sigma

```yaml
title: Oracle WebLogic Exploit-Path Probing and Encoded Traversal (TL-2026-4916)
id: 6f3b1c1e-52a4-4d1b-9a77-3c2e8a4b9d01
status: experimental
description: Detects web requests to Oracle WebLogic paths commonly abused for unauthenticated exploitation, and double-encoded traversal toward the WebLogic console, consistent with the Case C campaign against 1,300+ WebLogic candidates.
references:
  - https://thecyberexpress.com/ai-cyberattacks-on-japan-artex-three-cases/
  - https://thehackernews.com/2026/10/cyberstrikeai-uses-44-ai-agents-to.html
author: AII-Detector — ThreadLinqs Intelligence
date: 2026-10-31
tags:
  - attack.initial-access
  - attack.t1190
  - attack.reconnaissance
  - attack.t1595.002
logsource:
  category: webserver
detection:
  selection_path:
    cs-uri-stem|contains:
      - '/wls-wsat/'
      - '/_async/'
      - '/bea_wls_internal/'
      - '/uddiexplorer/'
      - '/management/weblogicmanagement/'
  selection_console:
    cs-uri-stem|contains: '/console/'
  selection_encoded:
    cs-uri-stem|contains:
      - '%252e%252e'
      - '%2e%2e'
  condition: selection_path or (selection_console and selection_encoded)
falsepositives:
  - Authorised vulnerability scanners or penetration tests against WebLogic
  - Legitimate WebLogic web-service clients that use the _async or wls-wsat endpoints internally
level: high
```

**Known false positives:**

- Authorised vulnerability scans or penetration tests against WebLogic servers
- Internal WebLogic web-service clients that legitimately call _async or wls-wsat endpoints

**Tuning notes:** Exclude known scanner and management source ranges via a lookup, and restrict to internet-facing WebLogic hosts. Treat ok_responses>0 or traversal_hits>0 as higher priority. Adjust index/sourcetype to the web, proxy or WAF source that fronts WebLogic.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- TL-2026-4916 Distributed Low-Frequency VPN and Edge Device Authentication Failures — Exploitation (locked: unlock with TL Creds)
- TL-2026-4916 Web Server or WebLogic Process Spawning Command Shell — Post-Exploitation (locked: unlock with TL Creds)
- TL-2026-4916 Wide IP-Block Sweep and CyberStrikeAI Host Traffic — C2 and Reconnaissance (locked: unlock with TL Creds)
- TL-2026-4916 Citrix NetScaler and F5 BIG-IP Management Path Abuse — Exploitation (locked: unlock with TL Creds)
- TL-2026-4916 Credential Harvesting From Configuration Files — Post-Exploitation (locked: unlock with TL Creds)
- TL-2026-4916 CyberStrikeAI Execution and AI-Generated Operator Script Artifacts — C2 and Tooling (locked: unlock with TL Creds)
- TL-2026-4916 Web Shell Written to Web Application Directory and Re-Created After Cleanup — Post-Exploitation (locked: unlock with TL Creds)
- TL-2026-4916 SSH Logon With Default Account After Failed Attempts — Lateral Movement (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (1 of 10)

Defanged, TLP:CLEAR.

- IP address: `212.11.64[.]250`

Full set of 10 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [AI's Role In Cyberattacks On Japan: Three Cases Beyond ARTEX](https://thecyberexpress.com/ai-cyberattacks-on-japan-artex-three-cases/)
- [CyberStrikeAI Uses 44 AI Agents to Target Japanese Organizations](https://www.esecurityplanet.com/threats/news-cyberstrikeai-44-ai-agents-japan-attacks-apac/)
- [CyberStrikeAI Uses 44 AI Agents (The Hacker News)](https://thehackernews.com/2026/10/cyberstrikeai-uses-44-ai-agents-to.html)
- [Three Japan-Focused Cyberattacks Show How Hackers Use AI (Security Affairs)](https://securityaffairs.com/?p=201913)
- [CyberStrikeAI tool adopted by hackers for AI-powered attacks (BleepingComputer)](https://www.bleepingcomputer.com/news/security/cyberstrikeai-tool-adopted-by-hackers-for-ai-powered-attacks/amp/)
- [ARTEX AI Tool Linked to Cyberattacks on Japanese Companies (eSecurityPlanet)](https://www.esecurityplanet.com/cybersecurity-threats/news-apac-artex-ai-cyberattacks-japan-companies/)
- [Chinese AI Tool Likely Used in Cyberattacks on Japan Firms (Nippon.com)](https://www.nippon.com/en/news/yjj2026102000795/)
- [CSA research note: CyberStrikeAI / ARTEX multi-agent offense](https://labs.cloudsecurityalliance.org/wp-content/uploads/2026/10/CSA_research_note_cyberstrikeai_artex_multi_agent_offense_20261028-csa-styled.pdf)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-4916