ARTEX command markers and first-touch recon chain in process command lines
Previdian's WebLogic honeypot captured ARTEX operators embedding a random marker in the first command they run (echo ARTEX479630; id; hostname; uname -r; nproc, base64-encoded in transit). If a payload like this ever executes on a real host, the marker or its encoded form lands in a process command line. Arm 1 matches the marker with its digit suffix, not the bare word. Arm 2 matches the base64 of echo ARTEX at all three alignments; case-sensitive, 13 characters, so collisions are negligible. Arm 3 matches the id; hostname; uname -r; nproc chain only from a server-side lineage, because that sequence alone is ordinary admin habit. Limits: the marker is attacker-controlled and spoofable, a nearby operator may drop it, and Previdian confirmed no host-level execution (the honeypot returned canned output), so this is a single-source tripwire, not a proven artifact.
Microsoft Sentinel (KQL)
