Reference VMT-INC-2026-0907 — this number is permanent and is the same one used in the open dataset, the incident feed and the API.

Where the money went — The pulled liquidity was followed through 1 transfer. Every hop below is a transaction anyone can look up.
  1. Hop 1: 0xa3eb7d…bebc sent funds to 0x7f5479…c2f9. That address is an address with no further recorded movement in the window read. transaction 0xdc40aebb12ee51571f40da03e2c913188a70df99ae053903a4afc6969a58e9d8

Recovery of lost funds cannot be promised by anyone. A service that promises recovery for a fee is, in the recorded pattern of such services, the second scam.

Open the evidence pack for VMT-INC-2026-0907 — one page carrying the token's facts, the verdict with the time it was computed, and the trace, formatted to print or save.

Report what happened to you

This goes to this site's operators and is not published. A report is one person's account; publishing it unverified would let anyone attach a loss to any address by typing it into a form.

Strike Robot SR

Base · 0x10c56f005a379f8eafc88ff5c3f40d30f0031ac9

Abandoned 31 Oct 2026

What we said, before

Scanned 23 Sep 2026. We published Elevated risk · 45/100.

This token's code does not resemble any we watched collapse. No one can create new tokens. This token is a thin copy pointing at code held somewhere else. Elevated risk.

The receipt

That verdict was computed from evidence run evr_6a6805cc3a6d7b2963d7356e, collected 23 Sep 2026, 10:10 UTC at finalized block 51683681. That run is append-only and pinned to a finalized block or slot: it is the reason the verdict above can be checked against the clock rather than believed.

What happened

An outcome check observed the trading pool drained on 31 Oct 2026, 03:01 UTC, 38.0 days after we first scanned it. Labels come from price and liquidity observations at fixed checkpoints, not from anyone's judgement about the project.

The full report for this token · Every token we watched collapse