Menu

From Commit Metadata to a Developer Target List
📰

From Commit Metadata to a Developer Target List

DEV Community: github·Ilja Krasnjanski·9 days ago
#fXCgpLDr
#devtogithub#technology#devto#dev#repository
Reading 0:00
15s threshold

The sender configuration pointed to two SQLite databases. I followed those references to the harvesting code and pools containing 79,698 and 62,667 rows, which together contain 142,365 distinct stored address strings associated with 27,698 repository values (the worker, configuration and read-only count records are summarized in E08 ), and the harvesting code collected those addresses from public commit metadata for use by the sender tooling.

One harvester fed two address pools

The harvester selects repositories by star range, walks their branches to extract author and committer addresses, then lowercases and trims them before filtering, and visits up to twenty branches per repository in the recorded implementation. Worker configurations partition the search. Scheduler and merge code consolidate results into two master pools. MITRE ATT&CK classifies this reconnaissance as gathering victim email addresses (T1589.002) .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.