Stratagems #17: Alex Set an AI Bait. The Catch Wasn't Code — It Was Someone Who Shouldn't Have Been Watching.

Toss out a brick to lure a jade gem.

— The 36 Stratagems, — MedTech signed a million-dollar AI monitoring contract. Alex built a hidden panel during training. When the panel failed, only he could read and write production.

— not tricking someone with a fake. It's putting out something real, with a signature only the right person would notice. Then waiting for them to tell you not just that they're watching — but that someone else was here before you.

🤖 AI Post-Mortem

CODE Kopieren

[36 Stratagems Tactical Database v3.2.5] Loaded

[Tactic Match] Throw Out a Brick to Get a Jade (#17)



Tactic Match: 91%

Operator: Alex (MedTech)

Action: Deployed a shadow training pipeline with

  embedded watermark.

Result: Exfiltration path confirmed. Third-party

  beacon discovered.



[Observation]

  → Operator used no internal resources beyond CI/CD

    routing config (12% weight).

  → Detection latency: up to 72h (matches sync cycle).

  → Subject's infrastructure includes an autonomous

    extraction pipeline active for ~5 months.



[Second Operator — Unidentified (Codename: P)]

  → Deployed 4 covert services across pipeline/storage/

    monitoring layers. Each disguised as standard infra

    component (labels: team/infra-optimization).

  → Resource footprint: 50m CPU / 128Mi each — below

    cost-optimization thresholds. Pod restarts absorbed

    silently by K8s.

  → Operational signature: Pure-function Python, minimal

    variable naming, zero comments — identifiable by code

    style alone.

  → Entry vector: Same week as ACL's own deployment.

    Operator entered alongside ACL, without ACL's knowledge.

  → Beacon method: PGP public key embedded in Base64-

    encoded config key (hmac_seed.yaml), disguised as

    routine initialization token.

  → Contact method: undocumented /healthz POST handler

    with header-based filtering. No logging. Single

    response received, confirming channel.



[Operator Assessment]

  → Role: Embedded observer. Autonomous deployment.

    No external command dependency.

  → Deployment strategy: 4 independently operable

    services, zero cross-dependency. If one is

    discovered, the remaining 3 continue operating.

  → Contact design: Asymmetric channel. P can receive

    indefinitely without revealing identity — the

    communication protocol does not require a response.

  → Risk posture: Ultra-low. No identity markers in any

    artifact. The PGP key itself is the only connection

    point — and it was planted as a deliberate beacon,

    not a leak.

  → Database note: This operator's deployment discipline

    matches the highest tier observed in this tactical

    database.



[⚠️ Anomaly — Critical]

  → Two unaffiliated operators have planted assets within

    ACL's infrastructure. Neither knows the other's identity.

  → Implication: ACL's infrastructure has been permeable

    to operators of a certain capability threshold for

    at least five months.

Next stratagem:

Vollständiger Original-Bericht

Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

↗ Original-Artikel auf dev.to lesen