National Cyber Warfare Foundation (NCWF)login

Threat-Actor-Usernames-Scrape for pivoting on cybercrime forum identities


0 user ratings
2026-11-09 13:27:00
milo
Red Team (CNA)
"Threat-Actor-Usernames-Scrape

A curated open repository collecting usernames and identity intelligence scraped from cybercrime forums, designed for CTI analysts and threat hunting teams conducting attribution research.








Toolspmedia/Threat-Actor-Usernames-Scrape — collected lists of usernames and identity intel scraped from cybercrime sources and forums
CategoryThreat intelligence data collection / OSINT pivot dataset
Primary UsePivoting on usernames observed in incidents to find matching accounts across cybercrime forums, enabling enrichment of actor profiles during authorized investigations
Safe UseStrictly for authorized threat intelligence research, internal investigations, and defensive CTI workflows by security teams; a username match is an investigative lead, never proof of identity
Telemetry NoteNone — this is a passive dataset; defenders use it to correlate artifacts already observed in their own logs and phishing lures

Unlike most repositories covered here, spmedia/Threat-Actor-Usernames-Scrape is not an executable utility at all — it is a data asset. The project aggregates usernames and associated identity intelligence scraped from cybercrime sources and forums into list form, and its value lies entirely in how an analyst consumes those lists rather than in any code that runs them. For teams building a CTI practice on a budget, this class of repository fills a real gap: commercial feeds are expensive, and the raw material of attribution — the recurring handles actors reuse across marketplaces, initial-access forums, and bragging channels — is often scattered beyond easy reach.


The repository's own metadata tells you what it wants to be. Its topic tags read like a curriculum for intelligence work: cti, threat-intelligence, threatintel-feeds, cyberthreatintelligence, osint, threat-hunting, enrichment, and scraping-websites. That taxonomy positions the collection at the intersection of OSINT reconnaissance and structured threatintel consumption, which is the correct framing — the dataset is an enrichment source, not an attack tool, and should never be treated as a target list.


Mechanically, the workflow the repo implies is straightforward. An analyst extracts an username from an artifact — a phishing email sender, a credential dump reviewed under authorized scope, a malware author handle found in a binary, a signature in a defacement — and checks it against the collected lists. A hit on a cybercrime forum gives the investigation a pivot point: the actor's posting history, preferred languages, marketplaces frequented, and contemporaries. From there, standard CTI tradecraft takes over: timeline construction, TTP mapping back to frameworks, and correlation against internal telemetry.


It is worth being precise about what a username match does and does not prove. Handle reuse is common but not universal, and impersonation, account resale, and deliberate false-flag handles are routine behaviors in these communities. The professional posture is to treat every hit from this dataset as a hypothesis requiring corroboration from independent sources — registration data, writing style, infrastructure overlap — before it enters a report. Attribution built on a single list lookup would not survive review, and the repository itself, framed as intel enrichment, invites exactly that cautious reading.


For defensive teams, the more interesting application is preventative. Feeding these username lists into monitoring logic — watching whether any of your executives' or administrators' public handles appear in fresh cybercrime-adjacent collections, or alerting when actor handles show up in your own inbound mail or abuse inboxes — converts a static list into an early-warning control. This is classic threat hunting hygiene: the dataset defines the needles, and your SIEM logs are the haystack. Because the lists are passive reference data, this use carries no operational risk to third parties.


Practitioners should also note the maintenance reality of scraped datasets. Sources churn — forums get seized, migrate domains, change registration requirements — so any list of this kind has a half-life. The honest approach is to record when you pulled the data, diff subsequent pulls to detect additions (newly observed handles are themselves a signal of fresh campaign activity), and archive superseded versions for longitudinal analysis. Treat the repository as a feed you periodically re-ingest rather than a one-time download.


There are governance considerations before onboarding it. The repository carries NOASSERTION licensing, which means the contents are not clearly licensed for redistribution; internal analytical use is one thing, but republishing the lists or embedding them wholesale into a commercial product would need a closer look at the provenance of each scraped source. The data also concerns real individuals — some of whom may be bystanders whose handles were scraped up incidentally — which reinforces the need to keep usage inside authorized, defensive workflows with documented purpose.


Integration-wise, the obvious pattern is to load the lists into whatever pivot surface your team already uses: a local MISP object corpus, a Maltego transform source, a simple Elasticsearch index, or even grep-able flat files for smaller shops. Pairing the handles with automated search across paste sites and archival services lets a single lead expand into a fuller actor footprint without any interaction with the criminal forums themselves — a meaningful operational-security benefit, since analysts who browse such forums directly risk exposure and attribution back to their organization.


With roughly 236 stars and a topic spread squarely aimed at the osint-reconnaissance and threatintelligence communities, the repository occupies a modest but genuine niche in the open-source intel ecosystem. It will not replace a commercial actor-profile database, and it should not be anyone's only source. But as free, community-curated pivot material for authorized investigators and defenders, it is exactly the kind of quiet infrastructure that makes attribution work on small teams feasible — provided every conclusion drawn from it is treated as a lead, not a verdict.



Official project repository for spmedia/Threat-Actor-Usernames-Scrape.

Download Tool

Educational analysis for authorized security professionals. Use only in controlled, authorized environments.






Source: OffensiveSec
Source Link: https://www.offsecblog.com/2026/11/threat-actor-usernames-scrape-for.html


Comments
new comment
Nobody has commented yet. Will you be the first?
 
Forum
Red Team (CNA)



Copyright 2012 through 2026 - National Cyber Warfare Foundation - All rights reserved worldwide.