feat(verify): owner decisions batch 09 (116-108; 112 parked); disputed-scenarios list for 19 unlabelled cases

This commit is contained in:
StellarCrow
2026-09-30 18:16:28 +02:00
parent ef8d064fd0
commit ca8d385dbf
2 changed files with 76 additions and 0 deletions
+14
View File
@@ -231,3 +231,17 @@ Taken case by case from `batches/contradictions-09.md`; evidence in `batches/bat
- **DB id 121** — accept: amount → ~$1M total per the victim (watch ~$400K; crypto unquantified, transfer unconfirmed: the phone with the wallet app was taken); kidnappings → 1 (gun to his face, ordered to the ground: not there voluntarily); targeting vector = surveillance of his address. - **DB id 121** — accept: amount → ~$1M total per the victim (watch ~$400K; crypto unquantified, transfer unconfirmed: the phone with the wallet app was taken); kidnappings → 1 (gun to his face, ordered to the ground: not there voluntarily); targeting vector = surveillance of his address.
- **DB id 118** — accept: violence_torture 1 stands firmly (kicked in the face), drop the note's hedge; amount $350,000 (captions say >$300,000); location → Brighton Beach, Brooklyn; sequence Authority Misuse → Home Invasion (package ruse); no crypto taken. - **DB id 118** — accept: violence_torture 1 stands firmly (kicked in the face), drop the note's hedge; amount $350,000 (captions say >$300,000); location → Brighton Beach, Brooklyn; sequence Authority Misuse → Home Invasion (package ruse); no crypto taken.
- **DB id 117** — accept: date → 4 February 2022 (day after the 3 Feb drive to Surat); amount → Rs 2 crore in cash brought to the trade (~$260K conversion); attackers → nine or more (Jha plus around eight); violence_torture → 1; weapons → unconfirmed (dacoity, no weapon described); sequence Malicious Invitation → P2P Trade Gone Wrong; targeting vector = acquaintance. - **DB id 117** — accept: date → 4 February 2022 (day after the 3 Feb drive to Surat); amount → Rs 2 crore in cash brought to the trade (~$260K conversion); attackers → nine or more (Jha plus around eight); violence_torture → 1; weapons → unconfirmed (dacoity, no weapon described); sequence Malicious Invitation → P2P Trade Gone Wrong; targeting vector = acquaintance.
- **DB id 116** — accept: date → 14 January 2022 (2 February is the arrests report); location → Pimpri Chinchwad, Pune (victim of Tathawade; hotel not located); amount → bitcoin worth Rs 300 crore, the police value of his holdings (drop the $50M, the record's own conversion); weapons → unconfirmed (none mentioned); theft → unconfirmed (released for fear of arrest, no transfer reported); sequence Kidnapping kept, Authority Misuse not applied; targeting vector = insider (constable in the Pune cybercrime cell).
- **DB id 114** — accept: traced; the record's date (26 January 2022) and description (insurance ruse, pushed out, locked the door, video) hold per freelanceinfos.fr of 27 January 2022 (https://freelanceinfos.fr/hasheur-agresse-domicile-cryptomonnaies/), TF1's 'two years ago' is loose; add freelanceinfos as a source and rewrite the summary from it (pending: pull the page into the dossier, checker pass); weapons stays 1 with note 'reported fake' (fibo-crypto timeline, on file under 473); violence_torture stays 0; sequence Costly Fame → Dodged Attack, attempted: Authority Misuse (insurance ruse at the door) and armed extortion at the victim's home.
- **DB id 113** — accept: date → Friday 14 January 2022 (inferred: HLN's report of Thursday 20 January places the arrests at the house on 'Friday morning' and a fourth arrest 'on Wednesday'; the date itself is not printed); victim → 34-year-old man and his 61-year-old mother (visiting); add the companion HLN article as a source for 'teacher' (https://www.hln.be/antwerpen/leraar-34-en-moeder-thuis-overvallen-en-mishandeld-daders-willen-codes-van-kluis-met-3-miljoen-euro-aan-bitcoins~ab232aa8/; pending: pull into the dossier); scenario and flags unchanged; outcome foiled, both victims hospitalised.
- **DB id 111** — accept: location → Lahore; amount → 20 million rupees demanded, 2.5 million rupees paid in bitcoin (about 9 BTC per CCN); description: replace "Over 60 BTC" (CCN sub-headline, does not match the body) with the body figures, 60 BTC logged as unresolved; sequence Authority Misuse → Kidnapping (official green plate, three police officials in the ransom); arrests → some (three police officials and two exchangers; Faisal Yousuf named, no arrest stated); outcome empty (release not reported); flags unchanged.
- **DB id 110** — accept: theft → unconfirmed (the release says the victims were "allegedly forced to make phone calls to transfer crypto currency"; no completed transfer stated; charge is Extortion); description → add "allegedly", "cells" plural; sequence Kidnapping kept (forced into cells and held about 30 hours; Kidnapping and Forcible Confinement both charged); whose cells they were is not stated, venue → cells in the same jail, ownership not stated (owner's reading: taken by force from where they were housed and held elsewhere in the jail); attackers are "11 inmates at the Thunder Bay District jail", victims are "two male victims" in a reported "inmate-on-inmate assault"; other flags unchanged; outcome: separated by correctional officers, all 11 charged.
- **DB id 108** — accept: attackers → four (Nicola, a former employee, and Gregory arrested; one Polish and one Russian man wanted); amount → Rp 5.8 billion, drop the $400k (no dollar figure in the source; CNN Indonesia uses Rp 5.8 billion both for the total loss including cash and for the crypto transfers, logged as unresolved); date kept at 11 December 2021 with the conflict logged ("Kamis (11/12)" in the Indonesian text, but 11 December 2021 was a Saturday; the English rendering reads "(12/11)"); sequence Home Invasion kept; flags unchanged; targeting vector = insider (former employee); held duration not stated.
- **DB id 112** — parked: waits on the disputed-scenarios decision (see the unlabelled cases section below and `disputed-scenarios.md`).
---
## Unlabelled cases — owner, 2026-09-30
- **DB ids 399, 409, 468, 11** — keep in the database (owner). They have no scenario only for lack of evidence on file; the label for each is still to be set.
- **19 disputed cases** (3, 6, 10, 57, 62, 66, 101, 105, 112, 198; 21, 349; 99, 383, 449, 450; 24, 45, 195) — pending: owner consulting colleagues on removal versus a new category. See `disputed-scenarios.md`. Case 112 of batch 09 waits on this.
+62
View File
@@ -0,0 +1,62 @@
# Disputed scenario assignments (2026-09-30)
19 cases where verification found that none of the eleven scenario labels fits. For each group the
question is the same: remove the cases from the database, or keep them under a new category.
Evidence per case: `scenario-sequences.json` (rationale, gaps) and the dossier in `sources/`.
Already decided by the owner: 399, 409, 468 and 11 stay in the database.
## A. Crypto ATM thefts (10)
Old label on all ten: Armed Robbery in Public Space. No weapon and nobody confronted, except where noted.
If kept, candidate category: Infrastructure Theft.
| ID | Place, year | What happened | Note |
|---|---|---|---|
| 3 | Netherlands, 2015 | Two ATMs stolen from closed businesses | Two thefts, weeks apart, in one record |
| 6 | Netherlands, 2015 | ATM holding 2,000 EUR taken from a café at night | Loss was banknotes |
| 10 | Netherlands, 2016 | ATM lifted and carried out, nobody present | |
| 57 | Canada, 2019 | Two masked men emptied an ATM in a closed shop at about 4 am | Loss was cash |
| 62 | USA, 2020 | Two men pried the machine open and took the cash box | Staff present, not confronted |
| 66 | USA, 2020 | ATM pried open in daylight | No article on file, record only |
| 101 | USA, 2021 | ATM dragged out of a closed liquor store with a van | |
| 105 | Spain, 2021 | Ram raid on a closed crypto shop at 3 am | Fire extinguisher aimed at bystanders during the getaway |
| 112 | USA, 2022 | Truck reversed through a closed gas station, ATM taken | |
| 198 | Australia, 2024 | Ram raid on a closed shopping centre, ATM taken | |
Related, already ruled: 158 (USA, attempted ATM theft that failed) is Dodged Attack with the attempt recorded.
A decision on this group should cover 158 as well.
## B. Mining hardware burglaries (2)
Old label on both: Armed Robbery in Public Space. If kept, candidate category: Infrastructure Theft.
| ID | Place, year | What happened | Note |
|---|---|---|---|
| 21 | Iceland, 2017 | About 600 ASICs taken from a data centre at night | Entry with a recruited security guard's codes |
| 349 | Abkhazia, 2021 | 20 mining servers ($10,000) stolen from an empty garage | |
## C. Burglaries of an empty home for a wallet or safe (4)
A specific holder was targeted; nobody was home. If kept, candidate category: Burglary (no occupant).
| ID | Place, year | What happened | Old label |
|---|---|---|---|
| 99 | New Zealand, 2021 | Safe said to hold $4M in crypto taken from a house under renovation | Armed Robbery in Public Space |
| 383 | USA, 2024 | Break-in to take a hardware wallet; victim's location tracked through iCloud | Home Invasion |
| 449 | USA, 2024 | Burglar travelled to Texas to take a hardware wallet with about 100 BTC | Home Invasion |
| 450 | USA, 2024 | Crew watched the house, waited for the iCloud signal that the victim had left, broke in to search for a hardware wallet | Home Invasion |
## D. Other (3)
| ID | Place, year | What happened | Old label | Question |
|---|---|---|---|---|
| 24 | USA, 2018 | A buyer fired a gun inside a condo during a Bitcoin sale; nothing stolen or demanded | Armed Robbery in Public Space | Violence at a trade with no theft: keep, and under which label? |
| 45 | USA, 2018 | Law-enforcement entry at a Localbitcoins trader's home; nothing on file describes the incident | Swatting | The record's own note says "lawful ... Take out of stats" |
| 195 | Unknown, 2024 | A 13-year-old's family doxed and their dog allegedly stolen after he rug-pulled a token | Kidnapping | No person was physically approached |
## Drafter's recommendation (not a decision)
- A and B: remove from the attack database, or move to a separate infrastructure list. Check 105 first.
- C: keep, with a new Burglary (no occupant) label.
- 45 and 195: remove. 24: keep.