lhy commited on
Commit
a8718a6
·
verified ·
1 Parent(s): 022d340

v2: revert value-altering substitutions from generation

Browse files

12,120 rows (3.72%), 13,754 characters. A substitution is reverted only where the numeral still parses as a number and that number is different: a digit reading as a different digit (10,650), the currency marker reading as a digit (2,006), a decimal point vanishing or reading as a comma (1,026), a thousands separator reading as a decimal point (72). Row count, row order and every label are unchanged. Letter obfuscation is untouched. Adds a research-only LICENSE and the full change log under corrections/.

LICENSE ADDED
@@ -0,0 +1,43 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ BitAbuse / BitViper / BitCore — Research Use Only
2
+
3
+ Copyright (c) 2025 Hanyong Lee, Chaelyn Lee, Yongjae Lee, Jaesung Lee
4
+
5
+ These datasets accompany:
6
+
7
+ Hanyong Lee, Chaelyn Lee, Yongjae Lee, and Jaesung Lee. 2025.
8
+ BitAbuse: A Dataset of Visually Perturbed Texts for Defending Phishing Attacks.
9
+ Findings of the Association for Computational Linguistics: NAACL 2025,
10
+ pages 4367-4384. https://doi.org/10.18653/v1/2025.findings-naacl.247
11
+
12
+ TERMS
13
+
14
+ 1. Research use only. As stated in the paper's Limitations and Ethics Statement:
15
+ "The datasets and models used in this paper are publicly available, but they
16
+ should not be used for purposes other than research." No other use is
17
+ permitted. In particular, no use may conduct, assist, or improve phishing,
18
+ fraud, or other attacks.
19
+
20
+ 2. Attribution. Cite the paper above in any work that uses these datasets.
21
+
22
+ 3. No redistribution. Do not mirror or republish these datasets elsewhere. Link
23
+ to the Hugging Face repositories instead, so that users receive the current
24
+ revision rather than a stale copy. Quoting individual examples in a paper or
25
+ report is not redistribution.
26
+
27
+ 4. Upstream data. The corpus derives from phishing reports collected from the
28
+ Bitcoin Abuse Database (https://www.bitcoinabuse.com, accessed 2023-04-30),
29
+ which was acquired by TRM Labs in October 2023 and folded into Chainabuse.
30
+ Nothing here grants rights over that upstream material, and users are
31
+ responsible for their own compliance with its terms.
32
+
33
+ 5. Content and identifiers. The texts are real phishing, sextortion and scam
34
+ messages, and contain abusive and sexually coercive language. They also carry
35
+ identifiers as they appeared in the original reports: bitcoin wallet
36
+ addresses in payment demands, email addresses, URLs, and residual mail
37
+ headers. Do not treat any of it as safe to reuse, and do not attempt to
38
+ contact, identify, or authenticate against anyone or anything named in the
39
+ data.
40
+
41
+ 6. No warranty. The datasets are provided "as is", without warranty of any kind,
42
+ express or implied. The authors accept no liability for any claim, damage or
43
+ other liability arising from their use.
README.md CHANGED
@@ -1,4 +1,7 @@
1
  ---
 
 
 
2
  dataset_info:
3
  features:
4
  - name: id
@@ -9,13 +12,170 @@ dataset_info:
9
  dtype: string
10
  splits:
11
  - name: train
12
- num_bytes: 72259353
13
  num_examples: 325580
14
- download_size: 45871484
15
- dataset_size: 72259353
16
  configs:
17
  - config_name: default
18
  data_files:
19
  - split: train
20
  path: data/train-*
 
 
21
  ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  ---
2
+ license: other
3
+ license_name: research-only
4
+ license_link: LICENSE
5
  dataset_info:
6
  features:
7
  - name: id
 
12
  dtype: string
13
  splits:
14
  - name: train
15
+ num_bytes: 72254030
16
  num_examples: 325580
17
+ download_size: 45679005
18
+ dataset_size: 72254030
19
  configs:
20
  - config_name: default
21
  data_files:
22
  - split: train
23
  path: data/train-*
24
+ size_categories:
25
+ - 100K<n<1M
26
  ---
27
+
28
+ # BitAbuse
29
+
30
+ Homoglyph-obfuscated abusive messages paired with their originals.
31
+ `text` is the obfuscated form, `label` the original.
32
+
33
+ BitAbuse is the union of two parts:
34
+ [BitCore](https://huggingface.co/datasets/AutoML/bitcore), restored by hand, and
35
+ [BitViper](https://huggingface.co/datasets/AutoML/bitviper), generated.
36
+
37
+ ```text
38
+ bitabuse (325,580) = bitcore (26,591) + bitviper (298,989)
39
+ ```
40
+
41
+ ## Revisions
42
+
43
+ | revision | rows | note |
44
+ |---|---:|---|
45
+ | `main` | 325,580 | original release, 2024-08-16 |
46
+ | `v2` | 325,580 | value-altering substitutions reverted, 2026-08 |
47
+
48
+ `main` is unchanged. Loading without a revision keeps the original behaviour.
49
+
50
+ ```python
51
+ load_dataset("AutoML/bitabuse", revision="v2")
52
+ ```
53
+
54
+ ## What v2 changes
55
+
56
+ Generation writes `text` from `label` by drawing, for each character, one of about
57
+ twenty randomised look-alike targets. For most characters that is the point: the pair
58
+ stays the same message, obfuscated. But a **numeral** can be drawn onto something that
59
+ still parses as a numeral, and then the pair stops being an obfuscation and becomes two
60
+ different claims.
61
+
62
+ ```text
63
+ label same old bs as usual for the last 3.5 months.
64
+ main sảme oⅠd ƅs aş usuaӀ for the lɵsț 3͒5 ӕoņths. <- reads as 35 months
65
+ v2 sảme oⅠd ƅs aş usuaӀ for the lɵsț 3.5 ӕoņths.
66
+ ```
67
+
68
+ The decimal point was drawn onto U+0352 COMBINING FERMATA, which attaches to the
69
+ preceding character and disappears. Neither a reader nor a parser can notice.
70
+
71
+ **The rule: revert a substitution when the numeral still parses as a number and that
72
+ number is different. Nothing else.**
73
+
74
+ | class | occurrences | example |
75
+ |---|---:|---|
76
+ | a digit reads as a different digit | 10,650 | `100%` → `109%` |
77
+ | the currency marker reads as a digit | 2,006 | `740$` → `7409` |
78
+ | a decimal point vanishes or reads as a comma | 1,026 | `3.5` → `3͒5`, `12.000` → `12،000` |
79
+ | a thousands separator reads as a decimal point | 72 | `$9,524` → `$9․524` |
80
+
81
+ **12,120 rows (3.72%), 13,754 characters.** Row count, row order and every `label` are
82
+ unchanged, so indices into `main` remain valid.
83
+
84
+ Every affected row is in the BitViper part. BitCore, whose pairs did not go through
85
+ generation, carries none of them. The same correction is published as
86
+ [`AutoML/bitviper`](https://huggingface.co/datasets/AutoML/bitviper) revision `v2`;
87
+ BitCore is unaffected and has no v2.
88
+
89
+ ## What v2 does not change
90
+
91
+ The test is whether the numeral still parses, not which codepoint was drawn.
92
+
93
+ ```text
94
+ 0 → u kept does not parse as a number; visibly corrupt
95
+ 0 → ս kept likewise, and identical in kind to 0 → u
96
+ 0 → 9 reverted parses, and the value changed
97
+ 2 → ߄ reverted NKO DIGIT FOUR parses as four
98
+ 0 → ߀ kept NKO DIGIT ZERO parses as zero, the same value
99
+ 5,000 → 5‚000 kept a low-9 quote still reads as a comma; the same number
100
+ 1,350 → 1350 kept a separator that vanishes costs no value
101
+ hello, world → hello. world kept not inside a numeral at all
102
+ ```
103
+
104
+ **Letter substitutions are never reverted.** They are the obfuscation the dataset exists
105
+ to study.
106
+
107
+ ```text
108
+ thinking → fhļnking visited → vjsited know → ķhow
109
+ ```
110
+
111
+ `main` carries 5,000,593 substitutions, of which 4,759,927 replace a letter. All of them
112
+ stay, along with punctuation obfuscation outside numerals.
113
+
114
+ ## What v2 still does not catch
115
+
116
+ The correction is deliberately narrow, and these remain in `v2`:
117
+
118
+ - **Currency swaps. 700 characters** where `$` was drawn onto `฿`, `₮` or `₵`. The number
119
+ survives and the currency changes. A reader sees a different symbol rather than a
120
+ different number, so these are treated as obfuscation.
121
+ - **Numerals broken beyond reading.** Where a digit was drawn onto a letter or a symbol,
122
+ the amount is unreadable rather than wrong, and v2 leaves it. `$500` → `ȿ5ȣ0` stays.
123
+ - **Wallet and bitcoin addresses**, which are obfuscated throughout in both revisions.
124
+ Do not treat any address in `text` as valid in either revision.
125
+
126
+ If your task needs a guaranteed-clean numeral, use `label`.
127
+
128
+ ## Known effect
129
+
130
+ **27 rows now have `text == label`.** Every substitution in those rows was a
131
+ value-altering one, so reverting them leaves the row uncorrupted. No row in `main` had
132
+ `text == label`. They are kept rather than dropped so that row indices stay aligned
133
+ with `main`. Filter them out if your task requires every row to be obfuscated.
134
+
135
+ ```python
136
+ ds = ds.filter(lambda r: r["text"] != r["label"])
137
+ ```
138
+
139
+ ## License and citation
140
+
141
+ Research use only. See `LICENSE`, and the paper's Ethics Statement: "The datasets
142
+ and models used in this paper are publicly available, but they should not be used
143
+ for purposes other than research."
144
+
145
+ The corpus derives from phishing reports collected from the Bitcoin Abuse Database.
146
+ Nothing here grants rights over that upstream material.
147
+
148
+ **Content warning.** These are real phishing, sextortion and scam messages. They
149
+ contain abusive and sexually coercive language, and carry identifiers from the
150
+ original reports — wallet addresses, email addresses, URLs and residual mail
151
+ headers. Do not attempt to contact, identify, or authenticate against anything
152
+ named in the data.
153
+
154
+ Redistribution is not permitted; link here rather than mirroring. Quoting
155
+ individual examples in a paper is not redistribution.
156
+
157
+ ```bibtex
158
+ @inproceedings{lee-etal-2025-bitabuse,
159
+ title = "{B}it{A}buse: A Dataset of Visually Perturbed Texts for Defending Phishing Attacks",
160
+ author = "Lee, Hanyong and Lee, Chaelyn and Lee, Yongjae and Lee, Jaesung",
161
+ editor = "Chiruzzo, Luis and Ritter, Alan and Wang, Lu",
162
+ booktitle = "Findings of the Association for Computational Linguistics: NAACL 2025",
163
+ month = apr,
164
+ year = "2025",
165
+ address = "Albuquerque, New Mexico",
166
+ publisher = "Association for Computational Linguistics",
167
+ url = "https://aclanthology.org/2025.findings-naacl.247/",
168
+ doi = "10.18653/v1/2025.findings-naacl.247",
169
+ pages = "4367--4384",
170
+ ISBN = "979-8-89176-195-7",
171
+ }
172
+ ```
173
+
174
+ ## Reproducing
175
+
176
+ `corrections/v2_changes.csv` lists every reverted character with its row id and position.
177
+ The correction is deterministic and derives entirely from `main`: for each position
178
+ where `label` holds a digit, `$`, or a separator between two digits, the drawn character
179
+ is classified as reading like a numeral, a decimal point, a comma, nothing at all
180
+ (combining marks and format characters), or visible damage; the position is reverted only
181
+ when the numeral still parses and its value differs.
corrections/v2_changes.csv ADDED
The diff for this file is too large to render. See raw diff
 
data/train-00000-of-00001.parquet CHANGED
@@ -1,3 +1,3 @@
1
  version https://git-lfs.github.com/spec/v1
2
- oid sha256:1a3649e8ada7af83154fcc3ace8621c8dd3d6af81933e0e2c6a27cbfad02f15f
3
- size 45871484
 
1
  version https://git-lfs.github.com/spec/v1
2
+ oid sha256:eb50c9670fcf81a2a0c48f0820bde0ef9c6d61e110abb7d9241ac5ea7891c159
3
+ size 45679005