Mint volume — issued rows per day; purple = day with Tracebit use events
Campaign lifecycle — 57 journey-fingerprint sigs, bar = first_seen → last_seen (sensor count in label)
Curated kill-chains — registry campaigns, maintained at briefing time
CREDENTIAL-DRAIN active
Mint→use pipeline, not a trap template. №35 ENDS THE TEN-WINDOW ZERO-USE STREAK: 7 creds used (28 events) — Feo Prest .175 used 6 of its hoard (16 ops: GetCallerIdentity success, ListFoundationModels denied) and SS-Net .211 used 1 (4 ops). The two top persistent collectors are now confirmed users. №32: 80.96.59.28 (ALEXHOST MD) mint→use from ONE host — 5x GetCallerIdentity success + 2 denied.
flowchart LR
MINT["Empty-IP mint burst<br/>on one node"] --> COLLECT["Collector harvest<br/>(forged AI-crawler UAs)"]
COLLECT -->|"minutes later"| USE["AWS use from egress IPs"]
USE --> S1["ConsoleLogin<br/>GetSigninToken<br/>GetCallerIdentity ✓24"]
USE --> S2["Denied recon ops<br/>GetAccount ×108<br/>DescribeInstances ×97<br/>ListUsers ×6"]
S1 --- POLICY["legacyOwnerAccess<br/>deny-all policy held"]
NIGHTAGENT dormant
DROPPER RETIRED 09-24: the nightagents/nightshell repo is 404 with its GHSAT token attached — the token was byte-identical across 14 windows. Eighth run (№28) was the campaign's first mint: 105.158.191.248, two full passes on farm 09-21, 1 credential issued, zero AWS use since. Idle three windows and counting; the phpunit verify body <?php echo "NightAgent";?> is the surviving fingerprint — a return must carry a NEW dropper URL.
flowchart LR
V["phpunit webshell verify<br/>NightAgent echo"] --> D["nightshell dropper<br/>RETIRED 09-24 — 404<br/>repo removed"]
D -.-> L["form login<br/>user=root&pass=wrong"]
L --> W["wp-batch SQLi<br/>UNION SELECT"]
W --> MINT["1 mint №28<br/>(zero AWS use)"]
METADATA-HUNT idle
Idle since №22 as a campaign; 7th marker-light window. №33: 3 @fs marker rows again (136.85.48.119, farm, 2nd window) with a 291-ev credential-family run (firebase/gcp-credentials, graphql, forged AI-crawler UAs, 3 mints) — resumption candidate.
№33: .246 farm census-without-mints (2,100 ev) + control 6 mints; pool .43.180 1 mint. Census cadence holds, mint output uneven.
flowchart LR
OP["/46 pool + external ops<br/>forged Googlebot/2.1"] --> SWEEP["1,042-path census<br/>12-s mint bursts"]
SWEEP --> MINT["/.env mints<br/>35 (№28)"]
MINT --> HOARD["Standing hoard<br/>~290+ creds, zero use"]
REGISTRY-HUNT active
LeakIX l9scan template. №33: 8 full-kit IPs (aidev 4 / farm 4, 41 ev) + l9explore 88-ev passes on control/frantech + FIRST lauterbourg visit (4 IPs, 39 ev, new 131323 UA variant); 9 mint rows at 1/IP.
flowchart LR
L9["LeakIX l9scan<br/>DO IP pool"] --> W1["WebLogic console"]
W1 --> W2["Confluence · WHM/cPanel"]
W2 --> DR["Docker registry enum<br/>/v2/internal/..."]
DR --> GR["/graphql introspection<br/>credential-canary hit"]
GR --> MINT["Mints 1/IP<br/>6 (№28)"]
№35: the ORIGINAL operator class returns — 185.19.40.202 (1337 Services GmbH NL) ran the registered 1,000-POST batch on lauterbourg-01-ts 00:14–00:15 UTC: preflight trio, then 1,000 system.multicall POSTs at ~23/s, fixed username admin vs rotating passwords (admin123, 12345678, pass123...), forged Chrome/78. First xmlrpc flood since №28; new node in the target set. №28: fifth operator 119.40.84.186 (BDCOM BD) burst→sustained: 18,063 xmlrpc + 18,063 wp-login POSTs over 6.5 h on netcup.
flowchart LR
OP["Operator rotates<br/>(1337 Svcs · GCP · Google BE · BDCOM BD)"] --> PRE["Preflight wlwmanifest<br/>+ wp/v2/users"]
PRE --> FLOOD["system.multicall flood<br/>1,600–18,063 POSTs"]
FLOOD --> WPL["wp-login phase<br/>one distinct password per POST"]
MALWARE-DICT active
Pfcloud 204.76.203.18 loop RESUMED №26 (first absence was №22): 2,059 ev control + 2,060 ru-edge in 27 h, byte-identical, 569 paths.
Named operator 69.5.20.14 (Byteplus, ID). №24: first idle window. Byte-identical 404-path passes, 9-UA rotation, /.aliyun/* sweep.
flowchart LR
OP["Byteplus 69.5.20.14<br/>9-UA rotation"] --> CENSUS["404-path byte-identical<br/>census + suffix fanout"]
CENSUS --> ALI["/.aliyun/* 21-path<br/>credential sweep"]
ALI --> ZERO["0 mints —<br/>recon only"]
SYNC-ENUM-WAVE active
№25 NEW: 8 IPs ran byte-identical 282-event WordPress user-enum passes (270 tarpit + 12 enum calls), Chrome/127 UA, staggered ~15 min across control, ru-edge, sponge 18:41-20:01 UTC 09-18. №24 2-IP run was the same shape; third run, promoted.
flowchart LR
Q["Scheduler queue<br/>1 IP per ~15-min slot"] --> P["Byte-identical 282-ev pass<br/>270 tarpit cycles + 12 enum calls"]
P --> N1["control"]
P --> N2["ru-edge"]
P --> N3["sponge"]
N1 --- ZERO["0 mints"]
MEGA-DICT active
PAUSE LIFTED №34: eleventh + twelfth replays in ONE window — 23.234.117.146 (tzulo US) 10:53 and 193.32.126.191 (31173 Services AB FR) 00:44, each 13,195 GETs/paths, identical sets. WORDLIST GREW +6 after the №32 freeze (/beacon_linux_amd64_p_<hex> ×2, /mass.sh, /lel.sh, /x64s, /mirai.arm64). №35: first miss since the lift — no replay in-window; a second miss re-opens the pause question.
flowchart LR
F["13,195-path IoT dropper-URL<br/>dictionary (shared artifact)"] --> R1["Replay 1: tzulo US<br/>13,195 in 52 s"]
F --> R2["Replay 2: 31173 FR<br/>13,195 in 1m54s"]
R1 --- B["NEW: /beacon_linux_amd64_p_*<br/>+/mass.sh · /lel.sh · /x64s<br/>+/mirai.arm64 — +6 after freeze"]
WP-BATCH family recurring
Not a standalone campaign since №12: wp-batch bodies ride inside INFOCREST-KIT / AKAMAI-CONFIG / NIGHTAGENT chains (SQLi via author_exclude UNION SELECT).
UN-MERGED from METADATA-HUNT in №33 per the registered trigger. №34–№35: two consecutive absences since the un-merge — the №34 rule fired, status is standing-paused. Un-pause on a 140.245.x/161.118.x run carrying the ~94-path core.
REGISTERED №33. №34: 105.115.10.78 returned solo (4 markers / 4 mints on ai-devbox-1) — its second run; 23.234.77.64 and the №32 originals absent. Operator ledger: 4 operators / 4 ASNs, every marker suffix fresh per run.
flowchart LR
P["GET /__ss_probe_<32-hex>__<br/>python-requests/2.31.0<br/>guarantees first-seen"] --> E["GET /.env → 200<br/>canary mint"]
E --> END["Run ends<br/>no POST · no fanout"]
CONFIG-SWEEP active
87.120.104.29 (Sino Worldwide NO, Googlebot/2.1 forgery). №33: SECOND mint run — 12 mints inside farm's 2,950-ev 1-minute burst + 6 on control's 1,239-ev census. №34: NO NEW RUN — the window's control rows and 6 mints are the №33 run seen through the 24-h seam.
flowchart LR
B["1-minute census burst<br/>1,600+ paths, 121 families"] --> W["wp-config · app-config ·<br/>aws-credentials paths"]
W --> MINT["/.env mints<br/>18 in-window"]
Mint → use sankey — sensor → minted → used-in-AWS / unused (all-time)
Network-layer recon — inbound sweeps on the fleet's public IPs (Arkime); not visible to the HTTP traps
Arkime window 2026-09-27 07:33:00 → 2026-09-28 07:34:04 UTC · 111,320 inbound sessions on 8 fleet public IPs. Identity is the client tool (fingerprint), never the source IP — sweep operators rotate addresses and keep the tool. Last column = source IPs per day.
fingerprint
campaign
sessions
src IPs
networks
countries
ports
src IPs/day
f555226df196…
LIBSSH-MASSSWEEP dispersed sweep (one port, many networks)