Skip to content
ARTEX.sh

Public ARTEX detection resources:who made each one, and how much to trust it.

Since the FBI alert, vendors, researchers and individuals have published rules and queries for spotting ARTEX. This page lists the ones this site could open and check, with who published each, when, what it covers and a plain trust label. For what to watch for in the first place, read the detection guide.

Checked

Before you use any of these

These resources are public, and most of them have not been reviewed by anyone outside their authors. Several say so themselves: MalwareMustDie says every rule in its pack ships as experimental, and ja1sh/artex-defense says it has only synthetic validation. Run new rules in monitor mode first, check the hits against your own traffic, tune them, and only then let them alert or block.

Trust labels on this page: vendor means a security company published it; researcher means a named researcher or group; community experiment means a new repository from an individual with little track record. This site checked that each item exists and what it says it covers. It did not test the rules.

From security vendors

These come with company posts that explain the activity behind them.

ResourceDateWhat it coversTrust
Cisco Talos, ARTEX and beyond2026-11-13Snort 3 rules 7:76, 7:77 and 7:78 and Snort 2 rules 1:67494, 1:67495 and 1:67496, for artifacts of the norma agent framework under ARTEX. 7:78 and 1:67496 are policy rules, off by default.Vendor
Elastic Security Labs, Inside the loop2026-11-13An ES|QL hunt for the user agents of several AI attack tool families, and use of Elastic's prebuilt threat intel IP indicator rule.Vendor
Datadog Security Labs, On the hunt for ARTEX2026-11-09Cloud SIEM detections and hunting advice for ARTEX activity in AWS accounts.Vendor
ExtraHop, What the network sees2026-11-12A network view of ARTEX traffic and a detection for known ARTEX domain names.Vendor
Cloudflare, Adapting to AI penetration testing orchestrators2026-11-13What Cloudflare sees from these tools and how to defend web apps. No rule IDs.Vendor
Censys, ARTEX: Agentic Asbestos2026-11-05A search to find exposed ARTEX consoles, useful for checking your own address space.Vendor
GitGuardian, Beyond ARTEX2026-11-09Fingerprint descriptions for finding your own ARTEX-family instances. No rules.Vendor
FBI FLASH-20261113-0012026-11-13Indicator tables, ATT&CK mapping and mitigations. No detection rules.Government
ThreatDefence, ARTEX Detections2026-11-20 checkedMIT repository with Sigma, KQL, Splunk, Elastic, Zeek, Suricata, YARA and osquery material. README reports syntax/conversion checks and a synthetic pcap; it explicitly says no captured ARTEX intrusion was used for testing. Baseline on your own data before alerting or blocking.Vendor; experimental, synthetic validation only
ReversingLabs, Threat Researcher's Notebook2026-11-18A CSV of 3,096 IP indicators that were actionable after triage (of 3,147), with the source of each, plus hashes for 184 operator binaries and console favicon hashes. ReversingLabs says to use the IPs as historical hunt indicators for July to November 2026, not as a blocklist, since some are shared VPN or Cloudflare WARP exits.Vendor
Hunt.io, ARTEX C2 feed2026-11-17A paid threat intel feed that Hunt.io says holds more than 4,200 ARTEX C2 endpoints (unique IP and port) seen in the past month, with host names, port, country and first and last seen dates, as JSON or GZ downloads. A free two-week trial covers the latest 7 days. Announced in a vendor post on X.Vendor, commercial

From named researchers

These are written by known researchers or small firms. They are often faster than vendors, and less reviewed.

ResourceDateWhat it coversTrust
MalwareMustDie, ARTEX detection signature pack (v1.1.5)First 2026-11-13; v1.1.4 on 2026-11-16; v1.1.5 on 2026-11-17Behavior-first rules in Sigma, KQL, Suricata 7, Snort 3, osquery, YARA and STIX, with a playbook. Licensed DRL 1.1. Every rule ships as experimental. Covered by Security Affairs on 2026-11-16. v1.1.4 added a WinRM and PsExec lateral-movement correlation that only fires after a foothold, and two fork user agents (MalwareMustDie post on X).Researcher
ja1sh/artex-defenseCreated 2026-11-15Seven behavioral Sigma rules, five correlations and two upstream fingerprints, with test fixtures and a validation playbook. Synthetic validation only, by its own account.Researcher
darkfibr/artex-forensics (Blackfish Security)2026-11-14Static analysis of the backdoored ARTEX Docker image and the deleted authorization guard, with a YARA rule for the image.Researcher
nuclei-templates pull request 17880Opened 2026-11-16A nuclei template that finds ARTEX consoles. Still open, not merged; its author says it was checked against two live hosts.Researcher, unmerged

Community experiments

New repositories from individuals. They may be useful as starting points. Read the code before you run anything from them.

  • Kshot3000/artex-defense-kit (created 2026-11-16, MIT): written by a solo developer. Guides and a self-scan script for finding your own exposed consoles and leaked secrets. No detection rules.
  • logsexe/artex-detection-as-code (created 2026-11-18, AGPL-3.0): compiles one Sigma rule tree into Splunk SPL and Microsoft Sentinel KQL in CI. Created the day this page was written.
  • mrvcode/artex-kql-hunting-playbook (created 2026-11-20, no license file, 0 stars when checked): a Spanish-language KQL playbook for Microsoft Sentinel and Defender XDR with 16 hunting queries, 3 templates, one scheduled analytics rule and an IoC catalog. Its README says the queries have not been run in production and asks you to check schemas, calibrate thresholds and add exclusions first.
  • Star-Ring-1F728/Reverse-Artex (created 2026-11-18, MIT, beta 0.1.0-beta.1, 1 star when checked): a beta tool that collects HTTP evidence from applications you own, flags suspicious activity and offers an optional protection SDK. The ARTEX simulation numbers in its README are self-claimed, from its own synthetic test setup, and not independently checked.

How to roll out a public rule

The same steps work for any rule on this page.

  1. 01

    Read it first

    Check what the rule matches and which logs it needs. A rule for a log source you do not collect will never fire.

  2. 02

    Run it in monitor mode

    Let it log matches without alerting or blocking for a week or two, and review every hit.

  3. 03

    Tune it to your traffic

    Add exceptions for your own scanners, authorized pentests and noisy tools. Keep a note of why each exception exists.

  4. 04

    Then alert, and track the source

    Turn on alerts once the false positives are known. Watch the source for updates, since several of these packs change every few days.

Questions

Is there an official ARTEX detection rule set?
No single official set exists. Vendors such as Cisco Talos, Elastic and Datadog publish their own, and researchers publish open packs.
Can I trust the community ARTEX rules?
Treat them as untested. Most say they are experimental or synthetically validated. Test them in monitor mode before you let them alert or block.
Will these rules catch every ARTEX attack?
No. Indicators change and forks rename things. Combine rules with the behavior signs in the detection guide.

Sources

Every claim on this page comes from these sources or from this site's own sourced pages. Open them for the full reports.

Follow the ARTEX story.

New forks, releases and reports, dated and sourced.

Isometric plane with glowing light columns