PurplelinkPL commited on
Commit
d9bd082
·
verified ·
1 Parent(s): 396cbcc

v1.0.0 camera-ready: keyed HMAC-SHA-256 author pseudonyms (corpus and sample), de-anonymized and validated Croissant, mixed per-source licenses, current datasheet

Browse files
README.md CHANGED
@@ -3,7 +3,9 @@ language:
3
  - en
4
  - zh
5
  - ru
6
- license: cc-by-4.0
 
 
7
  size_categories:
8
  - 1M<n<10M
9
  task_categories:
@@ -358,13 +360,13 @@ Each record in the main corpus contains:
358
 
359
  | Field | Type | Description |
360
  |-------|------|-------------|
361
- | `unified_id` | string | SHA-256-derived release identifier |
362
  | `source_dataset` | string | Input source file or dataset name |
363
  | `source_layer` | string | Normalized layer (see above) |
364
  | `text` | string | UTF-8 post/advisory text (max 8000 chars) |
365
  | `timestamp` | string | ISO 8601 publication datetime (UTC) |
366
  | `forum_id` | string | Source identifier |
367
- | `author_hash` | string | SHA-256 pseudonymized author |
368
  | `release_mode` | string | Governance mode (see below) |
369
 
370
  ## Release Governance
@@ -419,4 +421,6 @@ Paper: [arXiv:2605.03158](https://arxiv.org/abs/2605.03158) · Code: [github.com
419
 
420
  ## License
421
 
422
- Code and metadata: CC BY 4.0. Source text retains source-specific terms documented in the governance addendum and release manifest.
 
 
 
3
  - en
4
  - zh
5
  - ru
6
+ license: other
7
+ license_name: hackersignal-mixed
8
+ license_link: https://huggingface.co/datasets/BenAmpel/HackerSignal/blob/main/data/release/source_release_manifest.json
9
  size_categories:
10
  - 1M<n<10M
11
  task_categories:
 
360
 
361
  | Field | Type | Description |
362
  |-------|------|-------------|
363
+ | `unified_id` | string | Release identifier (truncated SHA-256 of provenance fields and the keyed author pseudonym) |
364
  | `source_dataset` | string | Input source file or dataset name |
365
  | `source_layer` | string | Normalized layer (see above) |
366
  | `text` | string | UTF-8 post/advisory text (max 8000 chars) |
367
  | `timestamp` | string | ISO 8601 publication datetime (UTC) |
368
  | `forum_id` | string | Source identifier |
369
+ | `author_hash` | string | Keyed HMAC-SHA-256 author pseudonym (unpublished key, rotated across major versions) |
370
  | `release_mode` | string | Governance mode (see below) |
371
 
372
  ## Release Governance
 
421
 
422
  ## License
423
 
424
+ Mixed. Code and metadata: CC BY 4.0. Source text keeps its source's terms, listed per source in `data/release/source_release_manifest.json`: US government public domain (NVD, CISA KEV), CC BY 4.0 (CVEfixes, GitHub Advisory), CC BY-SA 4.0 (ExploitDB-derived records), and dataset-specific or site terms for the rest. Where a source's terms conflict with this tag, the per-source terms govern.
425
+
426
+ Author pseudonyms changed in version 1.0.0 (keyed HMAC-SHA-256). `author_hash` and `unified_id` values from earlier revisions do not match this release.
data/release/source_release_manifest.json CHANGED
@@ -1,12 +1,12 @@
1
  {
2
  "dataset": "ETG: Exploit Text Graph",
3
- "version": "1.0.0-rc1",
4
  "doi": "TBD after immutable archive deposit",
5
- "maintainer": "Anonymous (see dataset repository issue tracker)",
6
  "issue_tracker": "GitHub issues for the accompanying repository",
7
  "source_manifest": "data/unified_hacker_communities_neurips_manifest.json",
8
- "release_file": "data/unified_hacker_communities_neurips_public.jsonl",
9
- "release_file_sha256": "bd409acd7ffc37ced54ac8d4808cb0a1339cb7cb8c7dd229e73b32d706805e4f",
10
  "croissant": "data/etg_croissant.json",
11
  "datasheet": "docs/datasheet.md",
12
  "governance": "docs/release_governance.md",
@@ -313,5 +313,6 @@
313
  "metadata_or_pointer_only": 13,
314
  "redistributable_text": 5,
315
  "research_text_with_terms": 9
316
- }
317
- }
 
 
1
  {
2
  "dataset": "ETG: Exploit Text Graph",
3
+ "version": "1.0.0",
4
  "doi": "TBD after immutable archive deposit",
5
+ "maintainer": "Benjamin M. Ampel (bampel@gsu.edu); issues via the dataset repository",
6
  "issue_tracker": "GitHub issues for the accompanying repository",
7
  "source_manifest": "data/unified_hacker_communities_neurips_manifest.json",
8
+ "release_file": "unified_hacker_communities_neurips_public.jsonl",
9
+ "release_file_sha256": "f2fd23989993a6b435767c760c0bc11b0351d13bfdbf64de02be79d3e7610576",
10
  "croissant": "data/etg_croissant.json",
11
  "datasheet": "docs/datasheet.md",
12
  "governance": "docs/release_governance.md",
 
313
  "metadata_or_pointer_only": 13,
314
  "redistributable_text": 5,
315
  "research_text_with_terms": 9
316
+ },
317
+ "author_pseudonymization": "keyed HMAC-SHA-256, key_id v1 (unpublished build-time key)"
318
+ }
docs/datasheet.md CHANGED
@@ -7,7 +7,7 @@
7
  ## Motivation
8
 
9
  **For what purpose was the dataset created?**
10
- HackerSignal was created to support NLP and machine learning research on cybersecurity threat intelligence. Specifically, it enables: (1) classifying text as exploit-relevant or not, (2) linking unstructured forum or advisory text to CVE records, and (3) predicting vulnerability severity from text. No prior *public* dataset links hacker community discourse, exploit databases, vulnerability advisories, and fix commits through a shared CVE identifier space at this scale.
11
 
12
  **Who created the dataset, and on behalf of which entity?**
13
  Anonymous (redacted for double-blind review). The dataset is an independent research contribution and is not created on behalf of any commercial entity.
@@ -36,16 +36,14 @@ It is a near-complete collection for sources with public APIs or structured feed
36
  - `text_raw`: source text before release cleaning, where available
37
  - `timestamp`: ISO 8601 publication datetime (UTC)
38
  - `forum_id`: source identifier string
39
- - `author_hash`: SHA-256 hash of source + author identifier (pseudonymised)
40
  - `thread_url`, `thread_title`, `section`: preserved when exposed by the source
41
 
42
  **Is there a label or target associated with each instance?**
43
- The base corpus has no labels. The five benchmark splits add labels:
44
- - Task 1: binary exploit-relevance label (0/1)
45
- - Task 2: CVE ID (for quality-controlled retrieval evaluation)
46
- - Task 3: severity class (0=low, 1=medium, 2=high, 3=critical)
47
- - Task 4: ternary hacker exploit label (0=non-exploit/noise, 1=vulnerability discussion, 2=actionable exploit)
48
- - Task 5: actionable exploit-signal label plus CVE ID when applicable
49
 
50
  **Is any information missing from individual instances?**
51
  All retained rows in the audited release have parseable timestamps, but some timestamps are placeholders or scrape dates when the original publication date was unavailable. Author information is pseudonymised and the original author string is not recoverable. Some imported sources contain garbled characters from source encoding errors.
@@ -58,10 +56,10 @@ Yes. The CVE index creates explicit linkages between instances and CVE records.
58
  - **Date noise**: Some timestamps reflect scraping date rather than original publication date (flagged in `meta.json` per source).
59
  - **Language noise**: The corpus is predominantly English, but `deepdarkcti` and several community sources contain multilingual posts (including Russian, Turkish, Persian, Arabic, and Chinese).
60
  - **Short rows**: The release contains 1,569,263 rows under eight tokens. These are useful for interaction analysis but should usually be filtered for text-only classification and retrieval tasks.
61
- - **Task-label caveats**: Task 1 labels are weak CVE-linkage labels sampled within source/split cells to remove source-membership confounding; the release includes a source-only diagnostic baseline and a 240-row manual audit packet for human adjudication. Task 2 is quality-controlled to remove unretrievable empty/high-risk rows, but its CVE labels are still metadata-derived rather than manually adjudicated. Task 3 strips explicit severity and CVSS label strings from benchmark input after label extraction; the automated leakage audit reports zero strict sanitized leakage hits. Task 4 uses weak ternary labels derived from CVE metadata and actionability cues, not human exploit-semantics labels. Task 5 positives are the actionable CVE-linked subset of Task 4 and should be interpreted as conservative actionable-signal metadata.
62
 
63
  **Is the dataset self-contained, or does it link to external resources?**
64
- The governed public release is self-contained for sources whose terms permit text redistribution. Sources with ambiguous or restrictive terms are released as metadata/pointer-only records following `docs/release_governance.md`: provenance, source IDs, timestamps, CVE references, text hashes, and text lengths are retained, while `text` and `text_raw` are withheld. The CVE linkage task (Task 2) uses NVD CVE descriptions as the corpus, which are included in the `nvd_posts.jsonl` file. No live external resources are required at inference time for redistributable-text records.
65
 
66
  **Does the dataset contain data that might be considered confidential?**
67
  No private communications, medical records, financial records, or government classified information is intentionally included. All text was collected from publicly accessible sources and no authentication was bypassed. Public availability does not eliminate privacy risk, so the release pseudonymises authors, documents source modes, supports takedown/correction requests, and can downgrade terms-ambiguous sources to metadata/pointer-only release.
@@ -87,7 +85,7 @@ Scripts were written and executed by the dataset authors. Collection occurred be
87
  Collection scripts ran between January 2026 and April 2026. The audited release contains timestamped records spanning 1988 to April 2026, with the bulk of structured NVD records beginning in 2002.
88
 
89
  **Were any ethical review processes conducted?**
90
- The dataset consists of publicly accessible OSINT data, but the release treats public accessibility as insufficient by itself. No personally identifiable information was deliberately collected. Author strings are pseudonymised via SHA-256 hashing. No IRB review was required for collection of public OSINT data under the authors' institution's guidelines; however, researchers who build on HackerSignal for studies involving inferences about individuals should consult their own IRB.
91
 
92
  **Did the individuals whose data is collected consent to collection?**
93
  Individuals did not provide study-specific consent. Participants posted to public internet forums or public reporting/advisory channels, and all sources were publicly indexed or exposed through public APIs. The release therefore minimizes identity signals, preserves provenance, and applies source-specific release modes rather than assuming that public visibility alone justifies unrestricted redistribution.
@@ -103,7 +101,7 @@ Individuals did not provide study-specific consent. Participants posted to publi
103
  - Encoding errors replaced with the Unicode replacement character (U+FFFD)
104
  - Source provenance normalized into `source_dataset`, `source_layer`, `forum_id`, optional thread/category fields, and release-mode manifests
105
  - Exact duplicates removed across sources by normalized-text SHA-256 fingerprint
106
- - Task 3 benchmark inputs strip explicit severity labels, CVSS score lines, and CVSS vectors after labels are extracted
107
  - Reviewer-facing audit packets and leakage/overlap/quality reports are generated under `data/audits/`
108
 
109
  **Was the raw data saved?**
@@ -114,14 +112,12 @@ Yes — the collection and preprocessing scripts are available in the `src/etg/c
114
 
115
  **Were any labels created by human annotators?**
116
  No. All labels are derived automatically:
117
- - Task 1 labels: within-source CVE linkage (positive if the source CVE index maps the post ID to a CVE; negative if the same source/split has no CVE-index link and no explicit CVE token)
118
- - Task 2 labels: CVE linkage from existing metadata in quality-controlled source datasets
119
- - Task 3 labels: severity strings extracted from structured advisory fields via regex
120
- - Task 4 labels: weak ternary labels from source CVE metadata and exploit/actionability cues
121
- - Task 5 labels: actionable-signal labels from Task 4 actionable CVE-linked records, with same-split non-actionable negatives
122
 
123
  **What mechanisms were used to validate labels?**
124
- Task 1: positives inherit the quality of each source's CVE index, and negatives are weak absence labels rather than manual non-exploit judgments. The benchmark balances positives and negatives within retained source/split cells; the source-only diagnostic now falls to chance AUC, which supports removal of the earlier source-membership shortcut. A 240-row stratified packet is prepared for manual adjudication and remains annotation-pending until human labels are filled. A separate LLM-assisted triage pass used two independent judge prompts and reached consensus on 231/240 rows, with 75.32% consensus agreement with the weak benchmark label; these are automated triage labels, not human validation. The two LLM judges had 96.25% raw agreement, Cohen's kappa 0.9188, Krippendorff's nominal alpha 0.9188, and Gwet's AC1 0.9304. Task 2: CVE linkages are provided by source metadata and retained only for source families with low or medium CVE-linkage audit risk (CISA KEV, CVEfixes, DTL Exploits, and HackerOne). The split requires at least eight query tokens and uses titles as fallback query evidence when a body snippet is missing. A 240-row CVE-link packet is prepared for manual precision auditing. The LLM-assisted triage pass reached consensus on 233/240 Task 2 rows and marked 115 consensus rows as correct CVE links; this automated audit is used to filter high-risk source families and prioritize human review rather than as a precision claim. The two LLM judges had 97.08% raw agreement, Cohen's kappa 0.9417, Krippendorff's nominal alpha 0.9418, and Gwet's AC1 0.9417. Task 3: severity strings were extracted from structured advisory headers; records without a parseable severity field were excluded, and explicit severity/CVSS tokens are stripped from model input after extraction. The leakage audit finds 29,836 strict raw hits and zero strict sanitized hits, with 10 warning phrases left for manual review. Task 4: labels are regenerated from transparent weak rules using CVE linkage and actionability cues, and should be treated as benchmark supervision rather than human exploit labels. Task 5: positives are Task 4 actionable records with CVE metadata; retrieval labels are source CVE metadata and inherit the same CVE-linkage caveats as Task 2.
125
 
126
  ---
127
 
@@ -143,9 +139,8 @@ Earlier, smaller versions of the hacker forum data were used in prior work (ISI
143
  - The forum sources skew toward English-language, Western cybersecurity communities. Threats emerging from non-English communities may be underrepresented.
144
  - High-volume historical forum and dark-market imports skew toward 2015-2017 or earlier. Newer public sources such as DeepDarkCTI, 0x00sec, HackerSploit, ParrotSec, and Hack The Box extend into 2026 but are smaller production slices.
145
  - CISA KEV covers only actively exploited vulnerabilities; using KEV alone as a "critical" proxy will over-represent critical labels relative to the true severity distribution.
146
- - Task 1 should not be interpreted as a fully manually validated exploit-semantics benchmark because labels are weak CVE-linkage labels and CVE-index absence is not a manual negative annotation.
147
- - Task 2 is easier and higher-quality than an all-source noisy linkage benchmark because empty GitHub Advisory rows and high-risk source families are filtered out; it should be interpreted as a quality-controlled metadata-linkage benchmark, not a manually validated CVE-link ground truth set.
148
- - Task 4 and Task 5 lean deliberately on hacker-community signals, but labels are weak and actionability is rare; macro-F1, per-class F1, and joint retrieval metrics are more informative than accuracy alone.
149
  - Some public forum/community sources may be released as metadata/pointer-only records depending on source terms and takedown requests.
150
 
151
  **Are there tasks for which the dataset should not be used?**
 
7
  ## Motivation
8
 
9
  **For what purpose was the dataset created?**
10
+ HackerSignal was created to support NLP and machine learning research on cybersecurity threat intelligence. Specifically, it enables: (1) CVE linkage retrieval — given exploit/advisory evidence text, retrieve the correct CVE description from a 340K-entry NVD corpus; (2) exploit type classification — 8-class vulnerability type prediction (injection, XSS, memory corruption, DoS, file inclusion, auth/access control, RCE, information disclosure) with temporal OOD evaluation; and (3) temporal CVE-disjoint generalization — prospective retrieval where the gold CVE sets in train and test are strictly disjoint. No prior *public* dataset links hacker community discourse, exploit databases, vulnerability advisories, and fix commits through a shared CVE identifier space at this scale.
11
 
12
  **Who created the dataset, and on behalf of which entity?**
13
  Anonymous (redacted for double-blind review). The dataset is an independent research contribution and is not created on behalf of any commercial entity.
 
36
  - `text_raw`: source text before release cleaning, where available
37
  - `timestamp`: ISO 8601 publication datetime (UTC)
38
  - `forum_id`: source identifier string
39
+ - `author_hash`: keyed HMAC-SHA-256 pseudonym of the source-namespaced author identifier (unpublished key; consistent within a release version)
40
  - `thread_url`, `thread_title`, `section`: preserved when exposed by the source
41
 
42
  **Is there a label or target associated with each instance?**
43
+ The base corpus has no labels. The three benchmark splits add labels:
44
+ - Task 1 (CVE-R): gold CVE identifier for retrieval evaluation (metadata-derived linkage to 340K NVD corpus; train <2022, val 2022–2023, test 2024+)
45
+ - Task 2 (ETC): 8-class exploit type label (injection, xss, memory_corruption, dos, file_inclusion, auth_access, rce, info_disclosure) derived from ExploitDB, 0day.today, and HackerOne metadata; train <2020, val 2020–2022, test ≥2023
46
+ - Task 3 (TG): gold CVE identifier for CVE-disjoint retrieval evaluation; splits defined by CVE publication year so that train and test gold CVE sets are strictly disjoint
 
 
47
 
48
  **Is any information missing from individual instances?**
49
  All retained rows in the audited release have parseable timestamps, but some timestamps are placeholders or scrape dates when the original publication date was unavailable. Author information is pseudonymised and the original author string is not recoverable. Some imported sources contain garbled characters from source encoding errors.
 
56
  - **Date noise**: Some timestamps reflect scraping date rather than original publication date (flagged in `meta.json` per source).
57
  - **Language noise**: The corpus is predominantly English, but `deepdarkcti` and several community sources contain multilingual posts (including Russian, Turkish, Persian, Arabic, and Chinese).
58
  - **Short rows**: The release contains 1,569,263 rows under eight tokens. These are useful for interaction analysis but should usually be filtered for text-only classification and retrieval tasks.
59
+ - **Task-label caveats**: Task 1 (CVE-R) and Task 3 (TG) labels are metadata-derived CVE linkages (source URL or CVE regex extraction), not manually adjudicated ground truth; CVE-index absence is not a manual negative annotation; a 240-row stratified manual audit packet is provided in `data/audits/` for transparency. Task 2 (ETC) labels are derived from structured metadata fields (ExploitDB exploit descriptions and tags, 0day.today exploit type fields, HackerOne vulnerability type prefixes) mapped to an 8-class taxonomy via deterministic rules; they are not human-validated annotations. All three tasks use temporal splits so that evaluation reflects prospective performance on data postdating training.
60
 
61
  **Is the dataset self-contained, or does it link to external resources?**
62
+ The governed public release is self-contained for sources whose terms permit text redistribution. Sources with ambiguous or restrictive terms are released as metadata/pointer-only records following `docs/release_governance.md`: provenance, source IDs, timestamps, CVE references, text hashes, and text lengths are retained, while `text` and `text_raw` are withheld. The CVE linkage retrieval tasks (Tasks 1 and 3) use NVD CVE descriptions as the retrieval corpus, which are included in the `nvd_posts.jsonl` file. No live external resources are required at inference time for redistributable-text records.
63
 
64
  **Does the dataset contain data that might be considered confidential?**
65
  No private communications, medical records, financial records, or government classified information is intentionally included. All text was collected from publicly accessible sources and no authentication was bypassed. Public availability does not eliminate privacy risk, so the release pseudonymises authors, documents source modes, supports takedown/correction requests, and can downgrade terms-ambiguous sources to metadata/pointer-only release.
 
85
  Collection scripts ran between January 2026 and April 2026. The audited release contains timestamped records spanning 1988 to April 2026, with the bulk of structured NVD records beginning in 2002.
86
 
87
  **Were any ethical review processes conducted?**
88
+ The dataset consists of publicly accessible OSINT data, but the release treats public accessibility as insufficient by itself. No personally identifiable information was deliberately collected. Author strings are pseudonymised with keyed HMAC-SHA-256 under an unpublished build-time key, rotated across major versions, so hashing candidate usernames does not reproduce a released pseudonym. Residual risk: pseudonyms stay consistent within a source, so one author's posts remain linkable to each other, and post text can still contain self-identifying content (signatures, handles, contact details). No IRB review was required for collection of public OSINT data under the authors' institution's guidelines; however, researchers who build on HackerSignal for studies involving inferences about individuals should consult their own IRB.
89
 
90
  **Did the individuals whose data is collected consent to collection?**
91
  Individuals did not provide study-specific consent. Participants posted to public internet forums or public reporting/advisory channels, and all sources were publicly indexed or exposed through public APIs. The release therefore minimizes identity signals, preserves provenance, and applies source-specific release modes rather than assuming that public visibility alone justifies unrestricted redistribution.
 
101
  - Encoding errors replaced with the Unicode replacement character (U+FFFD)
102
  - Source provenance normalized into `source_dataset`, `source_layer`, `forum_id`, optional thread/category fields, and release-mode manifests
103
  - Exact duplicates removed across sources by normalized-text SHA-256 fingerprint
104
+ - Near-duplicates estimated, not removed: 64-bit SimHash over 5-token shingles on a deterministic 3% sample (Hamming distance <= 3) puts about 8.2% of retained rows (~609K) in near-duplicate clusters; users can apply their own threshold
105
  - Reviewer-facing audit packets and leakage/overlap/quality reports are generated under `data/audits/`
106
 
107
  **Was the raw data saved?**
 
112
 
113
  **Were any labels created by human annotators?**
114
  No. All labels are derived automatically:
115
+ - Task 1 (CVE-R) labels: metadata-derived CVE linkages from source URL or CVE regex extraction; only low/medium CVE-linkage audit risk sources included (CISA KEV, CVEfixes, HackerOne)
116
+ - Task 2 (ETC) labels: exploit type from structured metadata fields (ExploitDB exploit descriptions and tags, 0day.today exploit type fields, HackerOne vulnerability type prefixes) mapped to an 8-class taxonomy via deterministic rules
117
+ - Task 3 (TG) labels: same CVE linkage derivation as Task 1; splits defined by CVE publication year to enforce strict gold-set disjointness
 
 
118
 
119
  **What mechanisms were used to validate labels?**
120
+ Task 1 (CVE-R) and Task 3 (TG): CVE linkages are provided by source metadata and retained only for source families with low or medium CVE-linkage audit risk (CISA KEV, CVEfixes, and HackerOne). The split requires at least eight query tokens and uses titles as fallback query evidence when a body snippet is missing. A 240-row CVE-link stratified packet is prepared for manual precision auditing. A LLM-assisted triage pass reached consensus on 233/240 CVE-R rows and marked 115 consensus rows as correct CVE links; this automated audit is used to filter high-risk source families and prioritize human review rather than as a precision claim. The two LLM judges had 97.08% raw agreement, Cohen's kappa 0.9417, Krippendorff's nominal alpha 0.9418, and Gwet's AC1 0.9417. Task 3 (TG) additionally verifies programmatically that |C_train ∩ C_test| = 0 (strict CVE disjointness). Task 2 (ETC): exploit type labels are mapped from structured metadata to an 8-class taxonomy via deterministic rules and validated against a 240-row stratified manual audit packet in `data/audits/`. Source families (ExploitDB, 0day.today, HackerOne) were chosen for their structured metadata quality; records without a parseable exploit type are excluded.
121
 
122
  ---
123
 
 
139
  - The forum sources skew toward English-language, Western cybersecurity communities. Threats emerging from non-English communities may be underrepresented.
140
  - High-volume historical forum and dark-market imports skew toward 2015-2017 or earlier. Newer public sources such as DeepDarkCTI, 0x00sec, HackerSploit, ParrotSec, and Hack The Box extend into 2026 but are smaller production slices.
141
  - CISA KEV covers only actively exploited vulnerabilities; using KEV alone as a "critical" proxy will over-represent critical labels relative to the true severity distribution.
142
+ - Task 1 (CVE-R) and Task 3 (TG) should not be interpreted as fully manually validated CVE-linkage benchmarks; labels are metadata-derived and CVE-index absence is not a manual negative annotation. Both tasks are quality-controlled by filtering to low/medium audit-risk source families (CISA KEV, CVEfixes, HackerOne).
143
+ - Task 2 (ETC) labels are derived from structured metadata rather than human annotation; the 8-class taxonomy covers the most common vulnerability types but may not capture rare or ambiguous classes equally well. Macro-F1 is the primary metric to surface per-class difficulty rather than accuracy alone.
 
144
  - Some public forum/community sources may be released as metadata/pointer-only records depending on source terms and takedown requests.
145
 
146
  **Are there tasks for which the dataset should not be used?**
etg_croissant.json CHANGED
@@ -2,20 +2,64 @@
2
  "@context": {
3
  "@language": "en",
4
  "@vocab": "https://schema.org/",
 
 
 
5
  "cr": "http://mlcommons.org/croissant/",
6
- "sc": "https://schema.org/",
7
- "dct": "http://purl.org/dc/terms/",
8
  "rai": "http://mlcommons.org/croissant/RAI/",
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
9
  "prov": "http://www.w3.org/ns/prov#"
10
  },
11
  "@type": "sc:Dataset",
12
- "dct:conformsTo": "http://mlcommons.org/croissant/RAI/1.0",
 
 
 
13
  "name": "HackerSignal",
14
- "description": "HackerSignal is a large-scale, multi-source dataset linking hacker community discourse, exploit databases, vulnerability advisories, and fix commits through a shared CVE identifier space. It spans 64 public forum/source identifiers across eight source layers, covers 1988\u20132026, and supports three benchmark tasks: CVE linkage retrieval, hacker signal detection with CVE grounding, and CVE-disjoint temporal generalization.",
15
  "url": "https://huggingface.co/datasets/BenAmpel/HackerSignal",
16
  "version": "1.0.0",
17
- "license": "https://creativecommons.org/licenses/by/4.0/",
18
- "usageInfo": "Code and metadata are CC BY 4.0 unless otherwise noted. Source text follows source-specific release modes documented in docs/release_governance.md; terms-ambiguous sources may be metadata_or_pointer_only.",
 
 
 
19
  "isAccessibleForFree": true,
20
  "datePublished": "2026",
21
  "inLanguage": [
@@ -23,13 +67,19 @@
23
  "zh",
24
  "ru"
25
  ],
26
- "citation": "Anonymous. (2026). HackerSignal \u2014 A Multi-Source Dataset for Hacker Community Analysis and CVE Linkage. Proceedings of NeurIPS Evaluations & Datasets Track.",
27
  "creator": [
28
  {
29
  "@type": "sc:Person",
30
- "name": "Anonymous",
31
- "email": "anonymous@example.com",
32
- "affiliation": "Anonymous"
 
 
 
 
 
 
33
  }
34
  ],
35
  "keywords": [
@@ -95,7 +145,7 @@
95
  "prov:startedAtTime": "2026-01-01",
96
  "prov:endedAtTime": "2026-04-30"
97
  },
98
- "rai:dataCollection": "Data was collected through four mechanisms: (1) Public APIs \u2014 NVD (NIST REST), GitHub Advisory Database (GraphQL), CISA KEV (JSON feed), HackerOne (HuggingFace Hub); (2) Public dataset ingestion \u2014 Gayanku (Kaggle), HackForums (Kaggle), DTL Exploits (GitHub/AZSecure), CVEfixes (Zenodo), DeepDarkCTI (GitHub), Kaeli hacker forums (Kaggle), CrackingArena (Kaggle), ZeroDay (GitHub); (3) Web scraping and public forum APIs \u2014 ExploitDB (CSV), Vulnerability-Lab, ZeroScience Lab, 0x00sec, HackerSploit, ParrotSec, Hack The Box, Go4Expert, Full Disclosure mailing list archive, Seebug; (4) Pre-processed datasets from HuggingFace Hub. All sources were publicly accessible at collection time; no authentication was bypassed.",
99
  "rai:dataCollectionType": "Web scraping, API, Surveys/Interviews",
100
  "rai:dataCollectionTimeframe": {
101
  "@type": "sc:DateTime",
@@ -105,37 +155,95 @@
105
  "rai:dataCollectionRawData": "Raw scraped HTML is not distributed. The processed JSONL files are the primary artifact. Collection and preprocessing scripts are available in the src/etg/collectors/ directory of the code repository.",
106
  "rai:dataCollectionMissingData": "Coverage is limited by public API availability, rate limits, and pagination depth for forum sources. Posts behind authentication walls are excluded. Some timestamps reflect scraping date rather than original publication date. Author information is pseudonymized and not recoverable. Some legacy forum imports do not preserve thread structure.",
107
  "rai:dataPreprocessingProtocol": "HTML tags stripped from forum post content; HTML entities unescaped; text truncated at 8000 characters; encoding errors replaced with Unicode replacement character (U+FFFD); source provenance normalized into source_dataset, source_layer, forum_id, and optional thread/category fields; exact duplicates removed across sources by normalized-text SHA-256 fingerprint; Task 3 benchmark inputs strip explicit severity labels, CVSS score lines, and CVSS vectors after label extraction; author strings pseudonymized via SHA-256 hashing of source-namespaced author identifiers.",
108
- "rai:dataLimitations": "Forum sources skew toward English-language Western cybersecurity communities; threats emerging from non-English communities may be underrepresented. High-volume historical forum imports skew toward 2015\u20132017 or earlier. Task 1 labels are weak CVE-linkage labels, not human exploit-semantics annotations; CVE-index absence is not a manual negative annotation. Task 2 signal detection uses weak labels derived from CVE metadata and actionability cues, not human annotations. Task 3 shares the same label methodology as Task 1 under a stricter CVE-disjoint constraint. Approximately 8.18% near-duplicate content remains after exact deduplication. The corpus contains 1,569,263 rows under eight tokens useful for interaction analysis but not text classification.",
109
- "rai:dataBiases": "English-language bias: the corpus is predominantly English with multilingual content (Russian, Turkish, Persian, Arabic, Chinese) limited to deepdarkcti and several community sources. Temporal bias: bulk of structured NVD records begin in 2002; high-volume forum imports cluster around 2015\u20132017. Source selection bias: only publicly indexed or API-accessible sources are included, potentially underrepresenting closed or invitation-only communities. CISA KEV covers only actively exploited vulnerabilities, over-representing critical severity relative to true distribution. Western-centric community selection may underrepresent threat actors operating primarily in non-English forums.",
110
- "rai:personalSensitiveInformation": "No private communications, medical records, financial records, or government classified information is intentionally included. All text was collected from publicly accessible sources. Author strings are pseudonymized via SHA-256 hashing of source-namespaced author identifiers; original author strings are not recoverable from the released dataset. Public forum usernames are not distributed. The release supports takedown and correction requests through the repository issue tracker.",
111
- "rai:dataUseCases": "Intended uses: defensive cybersecurity research, temporal retrieval, provenance-aware benchmark design, vulnerability lifecycle analysis, exploit prediction and early warning systems, cross-lingual threat intelligence, graph neural network research on exploit\u2013CVE\u2013fix commit knowledge graphs, and pre-training domain-adapted language models for cybersecurity. Prohibited uses: training systems for automated exploit code generation or malware; de-anonymizing forum participants or linking pseudonymous identities outside approved research protocols; operational blocking, law-enforcement, or employment decisions based solely on model outputs; republishing source text from metadata_or_pointer_only sources.",
112
  "rai:dataSocialImpact": "HackerSignal enables earlier detection of vulnerability exploitation activity by connecting hacker community discourse to the CVE lifecycle. Positive impacts include faster defensive response times and better understanding of exploit emergence patterns. Potential negative impacts include misuse for automated attack generation or targeting of individuals; these are mitigated through responsible-use restrictions, author pseudonymization, source-level release governance, and explicit prohibition of offensive applications in the dataset license.",
113
  "rai:dataReleaseMaintenancePlan": "Maintained by the dataset authors. Annual updates planned to incorporate new CVE records, CISA KEV entries, and newly published advisories. Versioning follows semantic versioning (MAJOR.MINOR.PATCH). All tagged versions remain available on HuggingFace Hub. Takedown and correction requests acknowledged within 10 business days; disputed text removed in next patch release. Sources that change terms post-release are downgraded to metadata_or_pointer_only until permissions are clarified.",
114
  "rai:hasSyntheticData": "none",
115
  "distribution": [
116
  {
117
  "@type": "cr:FileObject",
118
- "@id": "hf-repo",
119
- "name": "HuggingFace Repository",
 
120
  "contentUrl": "https://huggingface.co/datasets/BenAmpel/HackerSignal",
121
- "encodingFormat": "application/jsonlines",
122
- "sha256": "See versioned manifest checksums in the HuggingFace repository."
123
  },
124
  {
125
  "@type": "cr:FileObject",
126
  "@id": "public-jsonl",
127
  "name": "unified_hacker_communities_neurips_public.jsonl",
128
- "description": "Governed public release file enforcing source-level release modes from data/release/source_release_manifest.json.",
129
- "contentUrl": "https://huggingface.co/datasets/BenAmpel/HackerSignal/resolve/main/data/unified_hacker_communities_neurips_public.jsonl",
130
- "encodingFormat": "application/jsonlines"
 
131
  },
132
  {
133
  "@type": "cr:FileObject",
134
  "@id": "source-manifest",
135
  "name": "source_release_manifest.json",
136
- "description": "Machine-readable source provenance and release-mode manifest with checksums and row counts.",
137
  "contentUrl": "https://huggingface.co/datasets/BenAmpel/HackerSignal/resolve/main/data/release/source_release_manifest.json",
138
- "encodingFormat": "application/json"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
139
  }
140
  ],
141
  "recordSet": [
@@ -143,288 +251,569 @@
143
  "@type": "cr:RecordSet",
144
  "@id": "posts",
145
  "name": "posts",
146
- "description": "Forum posts, exploit advisories, vulnerability descriptions, and fix-commit messages from 64 public forum/source identifiers. Each record is one document. 7,447,646 exact-deduplicated rows spanning 1988\u20132026.",
147
  "field": [
148
  {
149
  "@type": "cr:Field",
150
  "@id": "posts/unified_id",
151
  "name": "unified_id",
152
- "description": "SHA-256-derived release identifier.",
153
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
154
  },
155
  {
156
  "@type": "cr:Field",
157
  "@id": "posts/source_dataset",
158
  "name": "source_dataset",
159
  "description": "Input source file or dataset name.",
160
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
161
  },
162
  {
163
  "@type": "cr:Field",
164
  "@id": "posts/source_layer",
165
  "name": "source_layer",
166
  "description": "Normalized layer: hacker_community, exploit_archive, vulnerability_reference, fix_commit_reference, exploit_qa_reference, or exploitation_reference.",
167
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
168
  },
169
  {
170
  "@type": "cr:Field",
171
  "@id": "posts/text",
172
  "name": "text",
173
  "description": "Full text of the post or advisory (UTF-8, max 8000 chars). Withheld for metadata_or_pointer_only sources.",
174
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
175
  },
176
  {
177
  "@type": "cr:Field",
178
  "@id": "posts/text_raw",
179
  "name": "text_raw",
180
  "description": "Source text before release cleaning, where available. Withheld for metadata_or_pointer_only sources.",
181
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
182
  },
183
  {
184
  "@type": "cr:Field",
185
  "@id": "posts/timestamp",
186
  "name": "timestamp",
187
  "description": "Publication date-time (ISO 8601, UTC).",
188
- "dataType": "sc:DateTime"
 
 
 
 
 
 
 
 
189
  },
190
  {
191
  "@type": "cr:Field",
192
  "@id": "posts/forum_id",
193
  "name": "forum_id",
194
  "description": "Source identifier (e.g. 'exploitdb', 'nvd', 'hackforums').",
195
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
196
  },
197
  {
198
  "@type": "cr:Field",
199
  "@id": "posts/author_hash",
200
  "name": "author_hash",
201
- "description": "SHA-256 hash of the source-namespaced author string (pseudonymised).",
202
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
203
  },
204
  {
205
  "@type": "cr:Field",
206
  "@id": "posts/release_mode",
207
  "name": "release_mode",
208
  "description": "Release-governance mode: redistributable_text, research_text_with_terms, metadata_or_pointer_only, or excluded.",
209
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
210
  },
211
  {
212
  "@type": "cr:Field",
213
  "@id": "posts/thread_url",
214
  "name": "thread_url",
215
  "description": "Source thread URL when exposed by the source.",
216
- "dataType": "sc:URL"
 
 
 
 
 
 
 
 
217
  },
218
  {
219
  "@type": "cr:Field",
220
  "@id": "posts/thread_title",
221
  "name": "thread_title",
222
  "description": "Thread or advisory title when available.",
223
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
224
  },
225
  {
226
  "@type": "cr:Field",
227
  "@id": "posts/section",
228
  "name": "section",
229
  "description": "Forum section or category when available.",
230
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
231
  }
232
  ]
233
  },
234
  {
235
  "@type": "cr:RecordSet",
236
- "@id": "cve_index",
237
- "name": "cve_index",
238
- "description": "Cross-source CVE linkage index mapping post IDs to CVE identifiers. One row per (post, CVE) pair. 360,004 rows contain CVE identifiers.",
239
  "field": [
240
  {
241
  "@type": "cr:Field",
242
- "@id": "cve_index/exploit_id",
243
- "name": "exploit_id",
244
- "description": "Foreign key to posts/unified_id.",
245
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
246
  },
247
  {
248
  "@type": "cr:Field",
249
- "@id": "cve_index/cve_id",
250
  "name": "cve_id",
251
- "description": "CVE identifier in the form CVE-YYYY-NNNNN.",
252
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
253
  },
254
  {
255
  "@type": "cr:Field",
256
- "@id": "cve_index/exploit_text",
257
- "name": "exploit_text",
258
- "description": "First 500 characters of the source post text.",
259
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
260
  },
261
  {
262
  "@type": "cr:Field",
263
- "@id": "cve_index/title",
264
- "name": "title",
265
- "description": "Advisory or post title.",
266
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
267
  },
268
  {
269
  "@type": "cr:Field",
270
- "@id": "cve_index/published",
271
- "name": "published",
272
- "description": "Publication date-time (ISO 8601, UTC).",
273
- "dataType": "sc:DateTime"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
274
  },
275
  {
276
  "@type": "cr:Field",
277
- "@id": "cve_index/source",
278
- "name": "source",
279
- "description": "Source identifier matching posts/forum_id.",
280
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
281
  }
282
  ]
283
  },
284
  {
285
  "@type": "cr:RecordSet",
286
- "@id": "task1_cve_linkage",
287
- "name": "task1_cve_linkage",
288
- "description": "Task 1 \u2014 CVE Linkage Retrieval (CVE-R). Cross-source temporally OOD entity grounding: given exploit/advisory evidence text, retrieve the correct NVD CVE entry from a corpus of 340,536 descriptions. Quality-controlled to remove unretrievable rows. 40,698 train / 2,551 val / 550 test.",
289
  "field": [
290
  {
291
  "@type": "cr:Field",
292
- "@id": "task1/id",
293
  "name": "id",
294
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
 
295
  },
296
  {
297
  "@type": "cr:Field",
298
- "@id": "task1/text",
299
  "name": "text",
300
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
 
301
  },
302
  {
303
  "@type": "cr:Field",
304
- "@id": "task1/cve_id",
305
- "name": "cve_id",
 
306
  "dataType": "sc:Text",
307
- "description": "Target CVE identifier in the corpus."
 
 
 
 
 
 
 
308
  },
309
  {
310
  "@type": "cr:Field",
311
- "@id": "task1/source",
312
  "name": "source",
313
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
 
314
  },
315
  {
316
  "@type": "cr:Field",
317
- "@id": "task1/timestamp",
318
  "name": "timestamp",
319
- "dataType": "sc:DateTime"
 
 
 
 
 
 
 
 
 
320
  },
321
  {
322
  "@type": "cr:Field",
323
- "@id": "task1/split",
324
  "name": "split",
 
325
  "dataType": "sc:Text",
326
- "description": "train / val / test"
 
 
 
 
 
 
 
 
 
 
327
  }
328
  ]
329
  },
330
  {
331
  "@type": "cr:RecordSet",
332
- "@id": "task2_signal_detection",
333
- "name": "task2_signal_detection",
334
- "description": "Task 2 \u2014 Hacker Signal Detection (HSD). Two-stage: detect actionable exploit signals from hacker community noise (10:1 negative ratio), then ground positives to NVD CVE. 4,202 train / 1,606 val / 407 test.",
335
  "field": [
336
  {
337
  "@type": "cr:Field",
338
- "@id": "task2/id",
339
  "name": "id",
340
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
 
341
  },
342
  {
343
  "@type": "cr:Field",
344
- "@id": "task2/text",
345
  "name": "text",
346
- "dataType": "sc:Text"
347
- },
348
- {
349
- "@type": "cr:Field",
350
- "@id": "task2/actionable_label",
351
- "name": "actionable_label",
352
- "dataType": "sc:Integer",
353
- "description": "0=not_actionable, 1=actionable_exploit_signal"
 
 
354
  },
355
  {
356
  "@type": "cr:Field",
357
- "@id": "task2/cve_id",
358
  "name": "cve_id",
 
359
  "dataType": "sc:Text",
360
- "description": "Primary CVE target for actionable records; empty for non-actionable."
 
 
 
 
 
 
 
361
  },
362
  {
363
  "@type": "cr:Field",
364
- "@id": "task2/source",
365
  "name": "source",
366
- "dataType": "sc:Text"
 
 
 
 
 
 
 
 
 
367
  },
368
  {
369
  "@type": "cr:Field",
370
- "@id": "task2/timestamp",
371
  "name": "timestamp",
372
- "dataType": "sc:DateTime"
 
 
 
 
 
 
 
 
 
373
  },
374
  {
375
  "@type": "cr:Field",
376
- "@id": "task2/split",
377
  "name": "split",
 
378
  "dataType": "sc:Text",
379
- "description": "train / val / test"
 
 
 
 
 
 
 
 
 
 
380
  }
381
  ]
382
  },
383
  {
384
  "@type": "cr:RecordSet",
385
- "@id": "task3_temporal_generalization",
386
- "name": "task3_temporal_generalization",
387
- "description": "Task 3 \u2014 Temporal Generalization (TG). Identical retrieval formulation to Task 1 but with strict CVE-disjoint constraint: C_train \u2229 C_test = \u2205. Split by CVE publication year (train <2022, test 2024+). 41,630 train / 1,776 val / 393 test.",
388
  "field": [
389
  {
390
  "@type": "cr:Field",
391
- "@id": "task3/id",
392
- "name": "id",
393
- "dataType": "sc:Text"
394
- },
395
- {
396
- "@type": "cr:Field",
397
- "@id": "task3/text",
398
- "name": "text",
399
- "dataType": "sc:Text"
400
- },
401
- {
402
- "@type": "cr:Field",
403
- "@id": "task3/cve_id",
404
  "name": "cve_id",
 
405
  "dataType": "sc:Text",
406
- "description": "Target CVE identifier (from 2024+ CVE set, disjoint from training CVEs)."
407
- },
408
- {
409
- "@type": "cr:Field",
410
- "@id": "task3/source",
411
- "name": "source",
412
- "dataType": "sc:Text"
413
- },
414
- {
415
- "@type": "cr:Field",
416
- "@id": "task3/timestamp",
417
- "name": "timestamp",
418
- "dataType": "sc:DateTime"
419
  },
420
  {
421
  "@type": "cr:Field",
422
- "@id": "task3/split",
423
- "name": "split",
 
424
  "dataType": "sc:Text",
425
- "description": "train / val / test"
 
 
 
 
 
 
 
426
  }
427
  ]
428
  }
429
- ]
430
- }
 
 
2
  "@context": {
3
  "@language": "en",
4
  "@vocab": "https://schema.org/",
5
+ "citeAs": "cr:citeAs",
6
+ "column": "cr:column",
7
+ "conformsTo": "dct:conformsTo",
8
  "cr": "http://mlcommons.org/croissant/",
 
 
9
  "rai": "http://mlcommons.org/croissant/RAI/",
10
+ "data": {
11
+ "@id": "cr:data",
12
+ "@type": "@json"
13
+ },
14
+ "dataType": {
15
+ "@id": "cr:dataType",
16
+ "@type": "@vocab"
17
+ },
18
+ "dct": "http://purl.org/dc/terms/",
19
+ "examples": {
20
+ "@id": "cr:examples",
21
+ "@type": "@json"
22
+ },
23
+ "extract": "cr:extract",
24
+ "field": "cr:field",
25
+ "fileProperty": "cr:fileProperty",
26
+ "fileObject": "cr:fileObject",
27
+ "fileSet": "cr:fileSet",
28
+ "format": "cr:format",
29
+ "includes": "cr:includes",
30
+ "isLiveDataset": "cr:isLiveDataset",
31
+ "jsonPath": "cr:jsonPath",
32
+ "key": "cr:key",
33
+ "md5": "cr:md5",
34
+ "parentField": "cr:parentField",
35
+ "path": "cr:path",
36
+ "recordSet": "cr:recordSet",
37
+ "references": "cr:references",
38
+ "regex": "cr:regex",
39
+ "repeated": "cr:repeated",
40
+ "replace": "cr:replace",
41
+ "sc": "https://schema.org/",
42
+ "separator": "cr:separator",
43
+ "source": "cr:source",
44
+ "subField": "cr:subField",
45
+ "transform": "cr:transform",
46
+ "wd": "https://www.wikidata.org/wiki/",
47
  "prov": "http://www.w3.org/ns/prov#"
48
  },
49
  "@type": "sc:Dataset",
50
+ "dct:conformsTo": [
51
+ "http://mlcommons.org/croissant/1.0",
52
+ "http://mlcommons.org/croissant/RAI/1.0"
53
+ ],
54
  "name": "HackerSignal",
55
+ "description": "HackerSignal is a large-scale, multi-source dataset linking hacker community discourse, exploit databases, vulnerability advisories, and fix commits through a shared CVE identifier space. It spans 64 public forum/source identifiers across eight source layers, covers 1988–2026, and supports three benchmark tasks: CVE linkage retrieval, hacker signal detection with CVE grounding, and CVE-disjoint temporal generalization.",
56
  "url": "https://huggingface.co/datasets/BenAmpel/HackerSignal",
57
  "version": "1.0.0",
58
+ "license": [
59
+ "https://creativecommons.org/licenses/by/4.0/",
60
+ "https://creativecommons.org/licenses/by-sa/4.0/"
61
+ ],
62
+ "usageInfo": "Mixed licensing. Code and metadata: CC BY 4.0. Source text keeps its source's terms, recorded per source in data/release/source_release_manifest.json (license_or_terms, release_mode): US government public domain (NVD, CISA KEV); CC BY 4.0 (CVEfixes, GitHub Advisory); CC BY-SA 4.0 (ExploitDB-derived records); dataset-specific or site terms for the remaining sources, which are released as research text with attribution or as metadata/pointer only. Where a source's terms conflict with the repository-level tag, the per-source terms govern.",
63
  "isAccessibleForFree": true,
64
  "datePublished": "2026",
65
  "inLanguage": [
 
67
  "zh",
68
  "ru"
69
  ],
70
+ "citation": "Ampel, B. M., & Samtani, S. (2026). HackerSignal: A Large-Scale Multi-Source Dataset Linking Hacker Community Discourse to the CVE Vulnerability Lifecycle. Advances in Neural Information Processing Systems (NeurIPS), Evaluations and Datasets Track.",
71
  "creator": [
72
  {
73
  "@type": "sc:Person",
74
+ "name": "Benjamin M. Ampel",
75
+ "email": "bampel@gsu.edu",
76
+ "affiliation": "J. Mack Robinson College of Business, Georgia State University"
77
+ },
78
+ {
79
+ "@type": "sc:Person",
80
+ "name": "Sagar Samtani",
81
+ "email": "ssamtani@iu.edu",
82
+ "affiliation": "Kelley School of Business, Indiana University"
83
  }
84
  ],
85
  "keywords": [
 
145
  "prov:startedAtTime": "2026-01-01",
146
  "prov:endedAtTime": "2026-04-30"
147
  },
148
+ "rai:dataCollection": "Data was collected through four mechanisms: (1) Public APIs — NVD (NIST REST), GitHub Advisory Database (GraphQL), CISA KEV (JSON feed), HackerOne (HuggingFace Hub); (2) Public dataset ingestion — Gayanku (Kaggle), HackForums (Kaggle), DTL Exploits (GitHub/AZSecure), CVEfixes (Zenodo), DeepDarkCTI (GitHub), Kaeli hacker forums (Kaggle), CrackingArena (Kaggle), ZeroDay (GitHub); (3) Web scraping and public forum APIs — ExploitDB (CSV), Vulnerability-Lab, ZeroScience Lab, 0x00sec, HackerSploit, ParrotSec, Hack The Box, Go4Expert, Full Disclosure mailing list archive, Seebug; (4) Pre-processed datasets from HuggingFace Hub. All sources were publicly accessible at collection time; no authentication was bypassed.",
149
  "rai:dataCollectionType": "Web scraping, API, Surveys/Interviews",
150
  "rai:dataCollectionTimeframe": {
151
  "@type": "sc:DateTime",
 
155
  "rai:dataCollectionRawData": "Raw scraped HTML is not distributed. The processed JSONL files are the primary artifact. Collection and preprocessing scripts are available in the src/etg/collectors/ directory of the code repository.",
156
  "rai:dataCollectionMissingData": "Coverage is limited by public API availability, rate limits, and pagination depth for forum sources. Posts behind authentication walls are excluded. Some timestamps reflect scraping date rather than original publication date. Author information is pseudonymized and not recoverable. Some legacy forum imports do not preserve thread structure.",
157
  "rai:dataPreprocessingProtocol": "HTML tags stripped from forum post content; HTML entities unescaped; text truncated at 8000 characters; encoding errors replaced with Unicode replacement character (U+FFFD); source provenance normalized into source_dataset, source_layer, forum_id, and optional thread/category fields; exact duplicates removed across sources by normalized-text SHA-256 fingerprint; Task 3 benchmark inputs strip explicit severity labels, CVSS score lines, and CVSS vectors after label extraction; author strings pseudonymized via SHA-256 hashing of source-namespaced author identifiers.",
158
+ "rai:dataLimitations": "Forum sources skew toward English-language Western cybersecurity communities; threats emerging from non-English communities may be underrepresented. High-volume historical forum imports skew toward 2015–2017 or earlier. Task 1 labels are weak CVE-linkage labels, not human exploit-semantics annotations; CVE-index absence is not a manual negative annotation. Task 2 signal detection uses weak labels derived from CVE metadata and actionability cues, not human annotations. Task 3 shares the same label methodology as Task 1 under a stricter CVE-disjoint constraint. Approximately 8.18% near-duplicate content remains after exact deduplication. The corpus contains 1,569,263 rows under eight tokens useful for interaction analysis but not text classification.",
159
+ "rai:dataBiases": "English-language bias: the corpus is predominantly English with multilingual content (Russian, Turkish, Persian, Arabic, Chinese) limited to deepdarkcti and several community sources. Temporal bias: bulk of structured NVD records begin in 2002; high-volume forum imports cluster around 2015–2017. Source selection bias: only publicly indexed or API-accessible sources are included, potentially underrepresenting closed or invitation-only communities. CISA KEV covers only actively exploited vulnerabilities, over-representing critical severity relative to true distribution. Western-centric community selection may underrepresent threat actors operating primarily in non-English forums.",
160
+ "rai:personalSensitiveInformation": "No private communications, medical records, financial records, or government classified information is intentionally included. All text was collected from publicly accessible sources. Author strings are pseudonymized with keyed HMAC-SHA-256 of source-namespaced author identifiers under an unpublished build-time key, rotated across major versions; without the key, hashing candidate usernames does not reproduce a released pseudonym. Pseudonyms stay consistent within a source, so one author's posts remain linkable to each other. Public forum usernames are not distributed. The release supports takedown and correction requests through the repository issue tracker.",
161
+ "rai:dataUseCases": "Intended uses: defensive cybersecurity research, temporal retrieval, provenance-aware benchmark design, vulnerability lifecycle analysis, exploit prediction and early warning systems, cross-lingual threat intelligence, graph neural network research on exploit–CVE–fix commit knowledge graphs, and pre-training domain-adapted language models for cybersecurity. Prohibited uses: training systems for automated exploit code generation or malware; de-anonymizing forum participants or linking pseudonymous identities outside approved research protocols; operational blocking, law-enforcement, or employment decisions based solely on model outputs; republishing source text from metadata_or_pointer_only sources.",
162
  "rai:dataSocialImpact": "HackerSignal enables earlier detection of vulnerability exploitation activity by connecting hacker community discourse to the CVE lifecycle. Positive impacts include faster defensive response times and better understanding of exploit emergence patterns. Potential negative impacts include misuse for automated attack generation or targeting of individuals; these are mitigated through responsible-use restrictions, author pseudonymization, source-level release governance, and explicit prohibition of offensive applications in the dataset license.",
163
  "rai:dataReleaseMaintenancePlan": "Maintained by the dataset authors. Annual updates planned to incorporate new CVE records, CISA KEV entries, and newly published advisories. Versioning follows semantic versioning (MAJOR.MINOR.PATCH). All tagged versions remain available on HuggingFace Hub. Takedown and correction requests acknowledged within 10 business days; disputed text removed in next patch release. Sources that change terms post-release are downgraded to metadata_or_pointer_only until permissions are clarified.",
164
  "rai:hasSyntheticData": "none",
165
  "distribution": [
166
  {
167
  "@type": "cr:FileObject",
168
+ "@id": "repo",
169
+ "name": "repo",
170
+ "description": "The HackerSignal Hugging Face dataset repository.",
171
  "contentUrl": "https://huggingface.co/datasets/BenAmpel/HackerSignal",
172
+ "encodingFormat": "git+https",
173
+ "sha256": "main"
174
  },
175
  {
176
  "@type": "cr:FileObject",
177
  "@id": "public-jsonl",
178
  "name": "unified_hacker_communities_neurips_public.jsonl",
179
+ "description": "Governed public corpus, one JSON record per line.",
180
+ "contentUrl": "https://huggingface.co/datasets/BenAmpel/HackerSignal/resolve/main/unified_hacker_communities_neurips_public.jsonl",
181
+ "encodingFormat": "application/jsonlines",
182
+ "sha256": "f2fd23989993a6b435767c760c0bc11b0351d13bfdbf64de02be79d3e7610576"
183
  },
184
  {
185
  "@type": "cr:FileObject",
186
  "@id": "source-manifest",
187
  "name": "source_release_manifest.json",
188
+ "description": "Per-source license terms, release modes and checksums.",
189
  "contentUrl": "https://huggingface.co/datasets/BenAmpel/HackerSignal/resolve/main/data/release/source_release_manifest.json",
190
+ "encodingFormat": "application/json",
191
+ "sha256": "d09c94ed2dc45d16848c3442c9539878de4661992b466a77aaf89b920b4c5a17"
192
+ },
193
+ {
194
+ "@type": "cr:FileObject",
195
+ "@id": "task1-corpus",
196
+ "name": "task1_corpus.jsonl",
197
+ "containedIn": {
198
+ "@id": "repo"
199
+ },
200
+ "contentUrl": "benchmark_v2/task1_cve_linkage/corpus.jsonl",
201
+ "encodingFormat": "application/jsonlines",
202
+ "sha256": "95c2449b77c2ff019bcef044ab2c77ae42f35aadff5751a5e15ab4e7c174736a"
203
+ },
204
+ {
205
+ "@type": "cr:FileObject",
206
+ "@id": "task3-corpus",
207
+ "name": "task3_corpus.jsonl",
208
+ "containedIn": {
209
+ "@id": "repo"
210
+ },
211
+ "contentUrl": "benchmark_v2/task3_temporal_generalization/corpus.jsonl",
212
+ "encodingFormat": "application/jsonlines",
213
+ "sha256": "875266e9e23a9e7862fe31c0d96ef1ed27828390ab34fa31a4f679feca5d60f8"
214
+ },
215
+ {
216
+ "@type": "cr:FileSet",
217
+ "@id": "task1-splits",
218
+ "name": "task1-splits",
219
+ "containedIn": {
220
+ "@id": "repo"
221
+ },
222
+ "encodingFormat": "application/jsonlines",
223
+ "includes": "benchmark_v2/task1_cve_linkage/[tv]*.jsonl",
224
+ "description": "task1_cve_linkage train.jsonl, val.jsonl and test.jsonl."
225
+ },
226
+ {
227
+ "@type": "cr:FileSet",
228
+ "@id": "task2-splits",
229
+ "name": "task2-splits",
230
+ "containedIn": {
231
+ "@id": "repo"
232
+ },
233
+ "encodingFormat": "application/jsonlines",
234
+ "includes": "benchmark_v2/task2_exploit_type/[tv]*.jsonl",
235
+ "description": "task2_exploit_type train.jsonl, val.jsonl and test.jsonl."
236
+ },
237
+ {
238
+ "@type": "cr:FileSet",
239
+ "@id": "task3-splits",
240
+ "name": "task3-splits",
241
+ "containedIn": {
242
+ "@id": "repo"
243
+ },
244
+ "encodingFormat": "application/jsonlines",
245
+ "includes": "benchmark_v2/task3_temporal_generalization/[tv]*.jsonl",
246
+ "description": "task3_temporal_generalization train.jsonl, val.jsonl and test.jsonl."
247
  }
248
  ],
249
  "recordSet": [
 
251
  "@type": "cr:RecordSet",
252
  "@id": "posts",
253
  "name": "posts",
254
+ "description": "Forum posts, exploit advisories, vulnerability descriptions, and fix-commit messages from 64 public forum/source identifiers. Each record is one document. 7,447,646 exact-deduplicated rows spanning 1988–2026. Each row's governing terms follow its source (source_dataset) in data/release/source_release_manifest.json (license_or_terms).",
255
  "field": [
256
  {
257
  "@type": "cr:Field",
258
  "@id": "posts/unified_id",
259
  "name": "unified_id",
260
+ "description": "Release identifier: truncated SHA-256 of provenance fields and the keyed author pseudonym.",
261
+ "dataType": "sc:Text",
262
+ "source": {
263
+ "fileObject": {
264
+ "@id": "public-jsonl"
265
+ },
266
+ "extract": {
267
+ "column": "unified_id"
268
+ }
269
+ }
270
  },
271
  {
272
  "@type": "cr:Field",
273
  "@id": "posts/source_dataset",
274
  "name": "source_dataset",
275
  "description": "Input source file or dataset name.",
276
+ "dataType": "sc:Text",
277
+ "source": {
278
+ "fileObject": {
279
+ "@id": "public-jsonl"
280
+ },
281
+ "extract": {
282
+ "column": "source_dataset"
283
+ }
284
+ }
285
  },
286
  {
287
  "@type": "cr:Field",
288
  "@id": "posts/source_layer",
289
  "name": "source_layer",
290
  "description": "Normalized layer: hacker_community, exploit_archive, vulnerability_reference, fix_commit_reference, exploit_qa_reference, or exploitation_reference.",
291
+ "dataType": "sc:Text",
292
+ "source": {
293
+ "fileObject": {
294
+ "@id": "public-jsonl"
295
+ },
296
+ "extract": {
297
+ "column": "source_layer"
298
+ }
299
+ }
300
  },
301
  {
302
  "@type": "cr:Field",
303
  "@id": "posts/text",
304
  "name": "text",
305
  "description": "Full text of the post or advisory (UTF-8, max 8000 chars). Withheld for metadata_or_pointer_only sources.",
306
+ "dataType": "sc:Text",
307
+ "source": {
308
+ "fileObject": {
309
+ "@id": "public-jsonl"
310
+ },
311
+ "extract": {
312
+ "column": "text"
313
+ }
314
+ }
315
  },
316
  {
317
  "@type": "cr:Field",
318
  "@id": "posts/text_raw",
319
  "name": "text_raw",
320
  "description": "Source text before release cleaning, where available. Withheld for metadata_or_pointer_only sources.",
321
+ "dataType": "sc:Text",
322
+ "source": {
323
+ "fileObject": {
324
+ "@id": "public-jsonl"
325
+ },
326
+ "extract": {
327
+ "column": "text_raw"
328
+ }
329
+ }
330
  },
331
  {
332
  "@type": "cr:Field",
333
  "@id": "posts/timestamp",
334
  "name": "timestamp",
335
  "description": "Publication date-time (ISO 8601, UTC).",
336
+ "dataType": "sc:DateTime",
337
+ "source": {
338
+ "fileObject": {
339
+ "@id": "public-jsonl"
340
+ },
341
+ "extract": {
342
+ "column": "timestamp"
343
+ }
344
+ }
345
  },
346
  {
347
  "@type": "cr:Field",
348
  "@id": "posts/forum_id",
349
  "name": "forum_id",
350
  "description": "Source identifier (e.g. 'exploitdb', 'nvd', 'hackforums').",
351
+ "dataType": "sc:Text",
352
+ "source": {
353
+ "fileObject": {
354
+ "@id": "public-jsonl"
355
+ },
356
+ "extract": {
357
+ "column": "forum_id"
358
+ }
359
+ }
360
  },
361
  {
362
  "@type": "cr:Field",
363
  "@id": "posts/author_hash",
364
  "name": "author_hash",
365
+ "description": "Keyed HMAC-SHA-256 pseudonym of the source-namespaced author string (unpublished key, rotated across major versions).",
366
+ "dataType": "sc:Text",
367
+ "source": {
368
+ "fileObject": {
369
+ "@id": "public-jsonl"
370
+ },
371
+ "extract": {
372
+ "column": "author_hash"
373
+ }
374
+ }
375
  },
376
  {
377
  "@type": "cr:Field",
378
  "@id": "posts/release_mode",
379
  "name": "release_mode",
380
  "description": "Release-governance mode: redistributable_text, research_text_with_terms, metadata_or_pointer_only, or excluded.",
381
+ "dataType": "sc:Text",
382
+ "source": {
383
+ "fileObject": {
384
+ "@id": "public-jsonl"
385
+ },
386
+ "extract": {
387
+ "column": "release_mode"
388
+ }
389
+ }
390
  },
391
  {
392
  "@type": "cr:Field",
393
  "@id": "posts/thread_url",
394
  "name": "thread_url",
395
  "description": "Source thread URL when exposed by the source.",
396
+ "dataType": "sc:URL",
397
+ "source": {
398
+ "fileObject": {
399
+ "@id": "public-jsonl"
400
+ },
401
+ "extract": {
402
+ "column": "thread_url"
403
+ }
404
+ }
405
  },
406
  {
407
  "@type": "cr:Field",
408
  "@id": "posts/thread_title",
409
  "name": "thread_title",
410
  "description": "Thread or advisory title when available.",
411
+ "dataType": "sc:Text",
412
+ "source": {
413
+ "fileObject": {
414
+ "@id": "public-jsonl"
415
+ },
416
+ "extract": {
417
+ "column": "thread_title"
418
+ }
419
+ }
420
  },
421
  {
422
  "@type": "cr:Field",
423
  "@id": "posts/section",
424
  "name": "section",
425
  "description": "Forum section or category when available.",
426
+ "dataType": "sc:Text",
427
+ "source": {
428
+ "fileObject": {
429
+ "@id": "public-jsonl"
430
+ },
431
+ "extract": {
432
+ "column": "section"
433
+ }
434
+ }
435
  }
436
  ]
437
  },
438
  {
439
  "@type": "cr:RecordSet",
440
+ "@id": "task1_queries",
441
+ "name": "task1_queries",
442
+ "description": "Task 1 (CVE linkage retrieval) queries with their gold CVE.",
443
  "field": [
444
  {
445
  "@type": "cr:Field",
446
+ "@id": "task1_queries/id",
447
+ "name": "id",
448
+ "description": "Query identifier.",
449
+ "dataType": "sc:Text",
450
+ "source": {
451
+ "fileSet": {
452
+ "@id": "task1-splits"
453
+ },
454
+ "extract": {
455
+ "column": "id"
456
+ }
457
+ }
458
+ },
459
+ {
460
+ "@type": "cr:Field",
461
+ "@id": "task1_queries/text",
462
+ "name": "text",
463
+ "description": "Query text.",
464
+ "dataType": "sc:Text",
465
+ "source": {
466
+ "fileSet": {
467
+ "@id": "task1-splits"
468
+ },
469
+ "extract": {
470
+ "column": "text"
471
+ }
472
+ }
473
  },
474
  {
475
  "@type": "cr:Field",
476
+ "@id": "task1_queries/cve_id",
477
  "name": "cve_id",
478
+ "description": "Gold CVE identifier.",
479
+ "dataType": "sc:Text",
480
+ "source": {
481
+ "fileSet": {
482
+ "@id": "task1-splits"
483
+ },
484
+ "extract": {
485
+ "column": "cve_id"
486
+ }
487
+ }
488
  },
489
  {
490
  "@type": "cr:Field",
491
+ "@id": "task1_queries/source",
492
+ "name": "source",
493
+ "description": "Source the query was drawn from.",
494
+ "dataType": "sc:Text",
495
+ "source": {
496
+ "fileSet": {
497
+ "@id": "task1-splits"
498
+ },
499
+ "extract": {
500
+ "column": "source"
501
+ }
502
+ }
503
  },
504
  {
505
  "@type": "cr:Field",
506
+ "@id": "task1_queries/timestamp",
507
+ "name": "timestamp",
508
+ "description": "Publication timestamp (ISO 8601).",
509
+ "dataType": "sc:Text",
510
+ "source": {
511
+ "fileSet": {
512
+ "@id": "task1-splits"
513
+ },
514
+ "extract": {
515
+ "column": "timestamp"
516
+ }
517
+ }
518
  },
519
  {
520
  "@type": "cr:Field",
521
+ "@id": "task1_queries/split",
522
+ "name": "split",
523
+ "description": "Split, from the file name (train, val or test).",
524
+ "dataType": "sc:Text",
525
+ "source": {
526
+ "fileSet": {
527
+ "@id": "task1-splits"
528
+ },
529
+ "extract": {
530
+ "fileProperty": "filename"
531
+ },
532
+ "transform": {
533
+ "regex": "^(train|val|test)\\.jsonl$"
534
+ }
535
+ }
536
+ }
537
+ ]
538
+ },
539
+ {
540
+ "@type": "cr:RecordSet",
541
+ "@id": "task1_corpus",
542
+ "name": "task1_corpus",
543
+ "description": "Task 1 retrieval corpus: 340,536 NVD CVE descriptions.",
544
+ "field": [
545
+ {
546
+ "@type": "cr:Field",
547
+ "@id": "task1_corpus/id",
548
+ "name": "id",
549
+ "description": "CVE identifier.",
550
+ "dataType": "sc:Text",
551
+ "source": {
552
+ "fileObject": {
553
+ "@id": "task1-corpus"
554
+ },
555
+ "extract": {
556
+ "column": "id"
557
+ }
558
+ }
559
  },
560
  {
561
  "@type": "cr:Field",
562
+ "@id": "task1_corpus/text",
563
+ "name": "text",
564
+ "description": "NVD description.",
565
+ "dataType": "sc:Text",
566
+ "source": {
567
+ "fileObject": {
568
+ "@id": "task1-corpus"
569
+ },
570
+ "extract": {
571
+ "column": "text"
572
+ }
573
+ }
574
  }
575
  ]
576
  },
577
  {
578
  "@type": "cr:RecordSet",
579
+ "@id": "task2_exploit_type",
580
+ "name": "task2_exploit_type",
581
+ "description": "Task 2 (exploit type classification, eight classes).",
582
  "field": [
583
  {
584
  "@type": "cr:Field",
585
+ "@id": "task2_exploit_type/id",
586
  "name": "id",
587
+ "description": "Query identifier.",
588
+ "dataType": "sc:Text",
589
+ "source": {
590
+ "fileSet": {
591
+ "@id": "task2-splits"
592
+ },
593
+ "extract": {
594
+ "column": "id"
595
+ }
596
+ }
597
  },
598
  {
599
  "@type": "cr:Field",
600
+ "@id": "task2_exploit_type/text",
601
  "name": "text",
602
+ "description": "Query text.",
603
+ "dataType": "sc:Text",
604
+ "source": {
605
+ "fileSet": {
606
+ "@id": "task2-splits"
607
+ },
608
+ "extract": {
609
+ "column": "text"
610
+ }
611
+ }
612
  },
613
  {
614
  "@type": "cr:Field",
615
+ "@id": "task2_exploit_type/label",
616
+ "name": "label",
617
+ "description": "Exploit type label (one of eight classes).",
618
  "dataType": "sc:Text",
619
+ "source": {
620
+ "fileSet": {
621
+ "@id": "task2-splits"
622
+ },
623
+ "extract": {
624
+ "column": "label"
625
+ }
626
+ }
627
  },
628
  {
629
  "@type": "cr:Field",
630
+ "@id": "task2_exploit_type/source",
631
  "name": "source",
632
+ "description": "Source the query was drawn from.",
633
+ "dataType": "sc:Text",
634
+ "source": {
635
+ "fileSet": {
636
+ "@id": "task2-splits"
637
+ },
638
+ "extract": {
639
+ "column": "source"
640
+ }
641
+ }
642
  },
643
  {
644
  "@type": "cr:Field",
645
+ "@id": "task2_exploit_type/timestamp",
646
  "name": "timestamp",
647
+ "description": "Publication timestamp (ISO 8601).",
648
+ "dataType": "sc:Text",
649
+ "source": {
650
+ "fileSet": {
651
+ "@id": "task2-splits"
652
+ },
653
+ "extract": {
654
+ "column": "timestamp"
655
+ }
656
+ }
657
  },
658
  {
659
  "@type": "cr:Field",
660
+ "@id": "task2_exploit_type/split",
661
  "name": "split",
662
+ "description": "Split, from the file name (train, val or test).",
663
  "dataType": "sc:Text",
664
+ "source": {
665
+ "fileSet": {
666
+ "@id": "task2-splits"
667
+ },
668
+ "extract": {
669
+ "fileProperty": "filename"
670
+ },
671
+ "transform": {
672
+ "regex": "^(train|val|test)\\.jsonl$"
673
+ }
674
+ }
675
  }
676
  ]
677
  },
678
  {
679
  "@type": "cr:RecordSet",
680
+ "@id": "task3_queries",
681
+ "name": "task3_queries",
682
+ "description": "Task 3 (CVE-disjoint temporal generalization) queries with their gold CVE.",
683
  "field": [
684
  {
685
  "@type": "cr:Field",
686
+ "@id": "task3_queries/id",
687
  "name": "id",
688
+ "description": "Query identifier.",
689
+ "dataType": "sc:Text",
690
+ "source": {
691
+ "fileSet": {
692
+ "@id": "task3-splits"
693
+ },
694
+ "extract": {
695
+ "column": "id"
696
+ }
697
+ }
698
  },
699
  {
700
  "@type": "cr:Field",
701
+ "@id": "task3_queries/text",
702
  "name": "text",
703
+ "description": "Query text.",
704
+ "dataType": "sc:Text",
705
+ "source": {
706
+ "fileSet": {
707
+ "@id": "task3-splits"
708
+ },
709
+ "extract": {
710
+ "column": "text"
711
+ }
712
+ }
713
  },
714
  {
715
  "@type": "cr:Field",
716
+ "@id": "task3_queries/cve_id",
717
  "name": "cve_id",
718
+ "description": "Gold CVE identifier.",
719
  "dataType": "sc:Text",
720
+ "source": {
721
+ "fileSet": {
722
+ "@id": "task3-splits"
723
+ },
724
+ "extract": {
725
+ "column": "cve_id"
726
+ }
727
+ }
728
  },
729
  {
730
  "@type": "cr:Field",
731
+ "@id": "task3_queries/source",
732
  "name": "source",
733
+ "description": "Source the query was drawn from.",
734
+ "dataType": "sc:Text",
735
+ "source": {
736
+ "fileSet": {
737
+ "@id": "task3-splits"
738
+ },
739
+ "extract": {
740
+ "column": "source"
741
+ }
742
+ }
743
  },
744
  {
745
  "@type": "cr:Field",
746
+ "@id": "task3_queries/timestamp",
747
  "name": "timestamp",
748
+ "description": "Publication timestamp (ISO 8601).",
749
+ "dataType": "sc:Text",
750
+ "source": {
751
+ "fileSet": {
752
+ "@id": "task3-splits"
753
+ },
754
+ "extract": {
755
+ "column": "timestamp"
756
+ }
757
+ }
758
  },
759
  {
760
  "@type": "cr:Field",
761
+ "@id": "task3_queries/split",
762
  "name": "split",
763
+ "description": "Split, from the file name (train, val or test).",
764
  "dataType": "sc:Text",
765
+ "source": {
766
+ "fileSet": {
767
+ "@id": "task3-splits"
768
+ },
769
+ "extract": {
770
+ "fileProperty": "filename"
771
+ },
772
+ "transform": {
773
+ "regex": "^(train|val|test)\\.jsonl$"
774
+ }
775
+ }
776
  }
777
  ]
778
  },
779
  {
780
  "@type": "cr:RecordSet",
781
+ "@id": "task3_corpus",
782
+ "name": "task3_corpus",
783
+ "description": "Task 3 retrieval corpus: NVD CVE descriptions.",
784
  "field": [
785
  {
786
  "@type": "cr:Field",
787
+ "@id": "task3_corpus/cve_id",
 
 
 
 
 
 
 
 
 
 
 
 
788
  "name": "cve_id",
789
+ "description": "CVE identifier.",
790
  "dataType": "sc:Text",
791
+ "source": {
792
+ "fileObject": {
793
+ "@id": "task3-corpus"
794
+ },
795
+ "extract": {
796
+ "column": "cve_id"
797
+ }
798
+ }
 
 
 
 
 
799
  },
800
  {
801
  "@type": "cr:Field",
802
+ "@id": "task3_corpus/text",
803
+ "name": "text",
804
+ "description": "NVD description.",
805
  "dataType": "sc:Text",
806
+ "source": {
807
+ "fileObject": {
808
+ "@id": "task3-corpus"
809
+ },
810
+ "extract": {
811
+ "column": "text"
812
+ }
813
+ }
814
  }
815
  ]
816
  }
817
+ ],
818
+ "citeAs": "@inproceedings{ampel2026hackersignal, title={{HackerSignal}: A Large-Scale Multi-Source Dataset Linking Hacker Community Discourse to the {CVE} Vulnerability Lifecycle}, author={Ampel, Benjamin M. and Samtani, Sagar}, booktitle={Advances in Neural Information Processing Systems (NeurIPS), Evaluations and Datasets Track}, year={2026}}"
819
+ }
hackersignal_sample_10k.jsonl CHANGED
@@ -1,3 +1,3 @@
1
  version https://git-lfs.github.com/spec/v1
2
- oid sha256:9cad9cdbdfdbc67ee4330f00029dc02a6a8cd4db04af815e2aca2de145b76c21
3
- size 24982654
 
1
  version https://git-lfs.github.com/spec/v1
2
+ oid sha256:d9192a3c67add44c444b258e1de1a7cf2fff73475199dd3c0847d363839f6b17
3
+ size 24989918
unified_hacker_communities_neurips_public.jsonl CHANGED
@@ -1,3 +1,3 @@
1
  version https://git-lfs.github.com/spec/v1
2
- oid sha256:bd409acd7ffc37ced54ac8d4808cb0a1339cb7cb8c7dd229e73b32d706805e4f
3
- size 12539636055
 
1
  version https://git-lfs.github.com/spec/v1
2
+ oid sha256:f2fd23989993a6b435767c760c0bc11b0351d13bfdbf64de02be79d3e7610576
3
+ size 12564492359