@aegis-scan/skills 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (69) hide show
  1. package/ATTRIBUTION.md +75 -0
  2. package/CHANGELOG.md +129 -0
  3. package/LICENSE +21 -0
  4. package/README.md +123 -0
  5. package/dist/bin.d.ts +3 -0
  6. package/dist/bin.d.ts.map +1 -0
  7. package/dist/bin.js +122 -0
  8. package/dist/bin.js.map +1 -0
  9. package/dist/commands/info.d.ts +5 -0
  10. package/dist/commands/info.d.ts.map +1 -0
  11. package/dist/commands/info.js +75 -0
  12. package/dist/commands/info.js.map +1 -0
  13. package/dist/commands/install.d.ts +7 -0
  14. package/dist/commands/install.d.ts.map +1 -0
  15. package/dist/commands/install.js +87 -0
  16. package/dist/commands/install.js.map +1 -0
  17. package/dist/commands/list.d.ts +7 -0
  18. package/dist/commands/list.d.ts.map +1 -0
  19. package/dist/commands/list.js +82 -0
  20. package/dist/commands/list.js.map +1 -0
  21. package/dist/index.d.ts +13 -0
  22. package/dist/index.d.ts.map +1 -0
  23. package/dist/index.js +13 -0
  24. package/dist/index.js.map +1 -0
  25. package/dist/skills-loader.d.ts +23 -0
  26. package/dist/skills-loader.d.ts.map +1 -0
  27. package/dist/skills-loader.js +213 -0
  28. package/dist/skills-loader.js.map +1 -0
  29. package/package.json +63 -0
  30. package/skills/defensive/README.md +9 -0
  31. package/skills/mitre-mapped/README.md +10 -0
  32. package/skills/offensive/snailsploit-fork/advanced-redteam/SKILL.md +148 -0
  33. package/skills/offensive/snailsploit-fork/ai-security/SKILL.md +592 -0
  34. package/skills/offensive/snailsploit-fork/basic-exploitation/SKILL.md +10783 -0
  35. package/skills/offensive/snailsploit-fork/bug-identification/SKILL.md +1256 -0
  36. package/skills/offensive/snailsploit-fork/crash-analysis/SKILL.md +12466 -0
  37. package/skills/offensive/snailsploit-fork/deserialization/SKILL.md +185 -0
  38. package/skills/offensive/snailsploit-fork/edr-evasion/SKILL.md +1806 -0
  39. package/skills/offensive/snailsploit-fork/exploit-dev-course/SKILL.md +428 -0
  40. package/skills/offensive/snailsploit-fork/exploit-development/SKILL.md +699 -0
  41. package/skills/offensive/snailsploit-fork/fast-checking/SKILL.md +487 -0
  42. package/skills/offensive/snailsploit-fork/file-upload/SKILL.md +822 -0
  43. package/skills/offensive/snailsploit-fork/fuzzing/SKILL.md +340 -0
  44. package/skills/offensive/snailsploit-fork/fuzzing-course/SKILL.md +2105 -0
  45. package/skills/offensive/snailsploit-fork/graphql/SKILL.md +209 -0
  46. package/skills/offensive/snailsploit-fork/idor/SKILL.md +608 -0
  47. package/skills/offensive/snailsploit-fork/initial-access/SKILL.md +1528 -0
  48. package/skills/offensive/snailsploit-fork/jwt/SKILL.md +276 -0
  49. package/skills/offensive/snailsploit-fork/keylogger-arch/SKILL.md +197 -0
  50. package/skills/offensive/snailsploit-fork/mitigations/SKILL.md +1351 -0
  51. package/skills/offensive/snailsploit-fork/oauth/SKILL.md +366 -0
  52. package/skills/offensive/snailsploit-fork/open-redirect/SKILL.md +487 -0
  53. package/skills/offensive/snailsploit-fork/osint/SKILL.md +399 -0
  54. package/skills/offensive/snailsploit-fork/osint-methodology/SKILL.md +434 -0
  55. package/skills/offensive/snailsploit-fork/parameter-pollution/SKILL.md +595 -0
  56. package/skills/offensive/snailsploit-fork/race-condition/SKILL.md +881 -0
  57. package/skills/offensive/snailsploit-fork/rce/SKILL.md +1069 -0
  58. package/skills/offensive/snailsploit-fork/request-smuggling/SKILL.md +773 -0
  59. package/skills/offensive/snailsploit-fork/shellcode/SKILL.md +477 -0
  60. package/skills/offensive/snailsploit-fork/sqli/SKILL.md +372 -0
  61. package/skills/offensive/snailsploit-fork/ssrf/SKILL.md +830 -0
  62. package/skills/offensive/snailsploit-fork/ssti/SKILL.md +349 -0
  63. package/skills/offensive/snailsploit-fork/vuln-classes/SKILL.md +1229 -0
  64. package/skills/offensive/snailsploit-fork/waf-bypass/SKILL.md +820 -0
  65. package/skills/offensive/snailsploit-fork/windows-boundaries/SKILL.md +15153 -0
  66. package/skills/offensive/snailsploit-fork/windows-mitigations/SKILL.md +14546 -0
  67. package/skills/offensive/snailsploit-fork/xss/SKILL.md +784 -0
  68. package/skills/offensive/snailsploit-fork/xxe/SKILL.md +996 -0
  69. package/skills/ops/README.md +6 -0
@@ -0,0 +1,434 @@
1
+ <!-- aegis-local: forked 2026-04-23 from SnailSploit/Claude-Red@c74d53e2938b59f111572e0819265a1e73029393; attribution preserved, see ATTRIBUTION.md -->
2
+
3
+ # SKILL: OSINT Methodology
4
+
5
+ ## Metadata
6
+ - **Skill Name**: osint-methodology
7
+ - **Folder**: offensive-osint-methodology
8
+ - **Source**: https://github.com/SnailSploit/offensive-checklist/blob/main/osint-method.md
9
+
10
+ ## Description
11
+ Structured OSINT methodology framework: target definition, source selection, collection workflows, data correlation, timeline reconstruction, and reporting. Use to guide systematic OSINT campaigns or teach OSINT methodology.
12
+
13
+ ## Trigger Phrases
14
+ Use this skill when the conversation involves any of:
15
+ `OSINT methodology, open source intelligence, target profiling, data correlation, OSINT workflow, intelligence collection, OSINT campaign, recon methodology`
16
+
17
+ ## Instructions for Claude
18
+
19
+ When this skill is active:
20
+ 1. Load and apply the full methodology below as your operational checklist
21
+ 2. Follow steps in order unless the user specifies otherwise
22
+ 3. For each technique, consider applicability to the current target/context
23
+ 4. Track which checklist items have been completed
24
+ 5. Suggest next steps based on findings
25
+
26
+ ---
27
+
28
+ ## Full Methodology
29
+
30
+ # OSINT Methodology
31
+
32
+ ## OpSec
33
+
34
+ ### Create a Sock Puppet
35
+
36
+ - Fake account that cannot be linked to you
37
+ - Build a posting history (post stuff, etc.)
38
+ - Resources
39
+ - [Effective Sock Puppets](https://medium.com/@unseeable06/creating-an-effective-sock-puppet-for-your-osint-investigation-95fdbb8b075a)
40
+ - [Ultimate Guide to Sock Puppets](https://osintteam.blog/the-ultimate-guide-to-sockpuppets-in-osint-how-to-create-and-utilize-them-effectively-d088c2ed6e36)
41
+ - [Fake Name Generator](https://www.fakenamegenerator.com/)
42
+ - [This Person does not Exist](https://thispersondoesnotexist.com/)
43
+ - Use separate browser profiles or isolation tools (e.g., **Firefox Multi‑Account Containers**) for any sock‑puppet activity.
44
+ - Acquire disposable VoIP/SMS numbers (e.g., **Burner**, **Silent Link**) to satisfy platform verification without exposing real phone numbers.
45
+ - Audit every browser extension before installation; supply‑chain attacks on popular add‑ons have targeted investigators since 2024.
46
+ - Use dedicated browser profiles/containers per case and persona; avoid logging into personal accounts.
47
+ - Prefer hardware‑backed passkeys for critical accounts; store recovery codes offline.
48
+ - Maintain a minimal chain‑of‑custody: timestamp actions, hash key artifacts, and record tool versions per case.
49
+
50
+ ## Cryptocurrency Investigation
51
+
52
+ ### Transaction Analysis
53
+
54
+ - Track transaction flows between wallets
55
+ - Identify clusters of related addresses
56
+ - Monitor large transfers and whale activity
57
+ - Use block explorers to trace fund movements
58
+ - Tools:
59
+ - Cielo: Multi-chain wallet tracking (EVM, Bitcoin, Solana, Tron)
60
+ - TRM: Create relationship graphs for addresses/transactions
61
+ - Arkham: Multichain explorer with entity labels, graph creation, and alerts
62
+ - MetaSleuth: Transaction visualization for retail users
63
+ - Range: CCTP bridge explorer
64
+ - Socketscan: EVM bridge explorer
65
+ - Pulsy: Bridge explorer aggregator
66
+ - Chainalysis: **Horizon 2.0** cross‑chain tracing suite (paid)
67
+ - Elliptic: **Lens** visual link explorer (launched Dec 2024)
68
+ - Most compliance suites now provide **real‑time bridge‑risk scoring** dashboards (e.g., TRM, Chainalysis)
69
+
70
+ #### Layer 2 / Rollup Analysis
71
+
72
+ - **zkSync Era / Polygon zkEVM**: Zero-knowledge proofs hide transaction details on L2; only deposit/withdrawal bridge events visible on L1. Use [zkSync Era Block Explorer](https://explorer.zksync.io/) and [PolygonScan zkEVM](https://zkevm.polygonscan.com/).
73
+ - **Arbitrum / Optimism**: Transactions batched and compressed; L2 state reconstructed from L1 calldata. Use [Arbiscan](https://arbiscan.io/) and [Optimistic Etherscan](https://optimistic.etherscan.io/). Check [L2Beat](https://l2beat.com/) for risk framework and technology stack.
74
+ - **StarkNet**: Cairo VM with STARK proofs; different address derivation. Use [Voyager](https://voyager.online/) or [StarkScan](https://starkscan.co/).
75
+ - **Base / Blast / Scroll**: OP Stack or ZK-rollups; similar challenges to above.
76
+ - **Privacy protocols on L2**:
77
+ - Aztec Network: Programmable privacy with noir circuits; limited block explorer visibility.
78
+ - Railgun: Privacy system for DeFi on Ethereum/Polygon/BSC; shielded pools obscure sender/receiver/amount.
79
+ - Privacy Pools: Proposed Tornado Cash successor with association sets; not yet deployed at scale.
80
+ - **Challenges**:
81
+ - Bridge mixers (Hop Protocol, Across, Stargate) create synthetic liquidity pools that break direct tracing; funds enter/exit via pool swaps.
82
+ - Cross-rollup transfers further obfuscate trails; requires tracking via bridge contracts and relayer infrastructure.
83
+ - Many L2s lack mature analytics tools; explorers show transactions but relationship graphs are sparse.
84
+ - **Methodology**:
85
+ - Start with L1 bridge events (deposits/withdrawals); these anchor L2 activity to known addresses.
86
+ - Use L2-specific explorers to trace activity within the rollup.
87
+ - For privacy protocols, focus on timing analysis, deposit/withdrawal clustering, and off-chain metadata (transaction memos, Tornado Cash-style notes).
88
+
89
+ #### Cautions (bridges and heuristics)
90
+
91
+ - Bridges/mixers/wrappers introduce mint/burn semantics; avoid assuming 1:1 flows without on‑chain proofs.
92
+ - MEV/sandwich and aggregator paths can create false "direct" trails; validate with multiple datasets.
93
+ - Cross‑label sanity: vendor labels can disagree; treat labels as hypotheses, not ground truth.
94
+ - **L2 finality**: Optimistic rollups have 7-day challenge periods; zkRollups finalize faster but proofs can be batched/delayed.
95
+
96
+ ### Wallet Profiling
97
+
98
+ - Analyze wallet age and activity patterns
99
+ - Check for connections to known entities
100
+ - Monitor balance changes over time
101
+ - Identify associated exchange accounts
102
+
103
+ ### Exchange Investigation
104
+
105
+ - Track deposits/withdrawals
106
+ - Monitor trading patterns
107
+ - Identify linked accounts
108
+ - Check for regulatory compliance
109
+
110
+ ### NFT Investigation
111
+
112
+ - Track ownership history
113
+ - Monitor sales and transfers
114
+ - Analyze metadata and hidden content
115
+ - Identify connected wallets and marketplaces
116
+
117
+ ## Image Analysis
118
+
119
+ - Contextual Analysis
120
+ - Use multiple reverse image search engines to find matches or similar images:
121
+ - [Google Images](https://images.google.com/) / **Google Lens** (note: Google Lens now requires authentication for some features; use incognito/sock-puppet account)
122
+ - [Yandex Images](https://yandex.com/images/)
123
+ - [Bing Image Match](https://www.bing.com/images/)
124
+ - [TinEye](https://tineye.com/)
125
+ - [Copyseeker](https://copyseeker.com/) AI‑based reverse‑image search engine
126
+ - [Perplexity Pro](https://www.perplexity.ai/) with image upload: AI-powered contextual analysis and web search
127
+ - Use browser extensions for quick searches:
128
+ - [RevEye Reverse Image Search](https://chrome.google.com/webstore/detail/reveye-reverse-image-sear/kejaocbebojdmebagkjghljkeefgimdj)
129
+ - [Search by Image](https://chromewebstore.google.com/detail/search-by-image/cnojnbdhbhnkbcieeekonklommdnndci) (multi-engine support)
130
+ - Change search terms and time to narrow down the possible results
131
+ - You can leverage [FakeNews Debunker Extension](https://chromewebstore.google.com/detail/fake-news-debunker-by-inv/mhccpoafgdgbhnjfhkcmgknndkeenfhe) as well
132
+ - [Picarta](https://picarta.ai/) might help with geolocation as well
133
+ - Check for embedded metadata (EXIF data) that may contain geolocation or device information:
134
+ - [ExifTool](https://exiftool.org/)
135
+ - [Jeffrey's Image Metadata Viewer](http://exif.regex.info/exif.cgi)
136
+ - [EXIF Viewer Pro](https://chrome.google.com/webstore/detail/exif-viewer-pro/mmbhfeiddhndihdjeganjggkmjapkffm)
137
+ - Foreground
138
+ - Signs, license plates, clothing styles, vegetation, and weather conditions.
139
+ - Background
140
+ - Landmarks, unique buildings, mountains, bodies of water, and infrastructure.
141
+ - Map Markings
142
+ - Flora and fauna types, which can indicate geographic regions.
143
+ - Seasonal indicators like snow, foliage, or daylight hours.
144
+ - Trial and Error
145
+ - Manually compare features from the image with maps and street views.
146
+ - Use platforms like `Google Street View`, `Bing Streetside`, and `Yandex Panorama` to virtually explore locations.
147
+ - Employ [Overpass Turbo](https://overpass-turbo.eu/)
148
+ - Use Snap Map public stories for area‑based context pivots.
149
+ - Consider Google Earth Studio for stabilized timelapse and bearing estimation.
150
+ - Pull Text from Image
151
+ - you can use google or Yandex OCR to pull text from image
152
+ - you can also search that text alongside your image for better results
153
+ - Transcript extraction for video (YouTube): fetch captions to improve keyword and entity search.
154
+
155
+ ### Image Forensics
156
+
157
+ - Analyze images for signs of manipulation or to uncover hidden details.
158
+ - Tools
159
+ - [Forensically](https://29a.ch/photo-forensics/)
160
+ - [FotoForensics](http://fotoforensics.com/)
161
+ - [Bellingcat Photo Checker](https://photo-checker.bellingcat.com/)
162
+ - [Sensity AI Deepfake Monitor](https://platform.sensity.ai/)
163
+ - [Exposing.ai](https://exposing.ai/) facial‑dataset search
164
+ - C2PA verification: [Adobe Content Credentials Verify](https://verify.contentauthenticity.org/) and `c2patool`
165
+ - Techniques
166
+ - Error Level Analysis (ELA)
167
+ - Metadata examination
168
+ - Clone detection
169
+ - Noise analysis
170
+
171
+ ### Mountain Geolocation
172
+
173
+ - Use tools to identify mountain peaks and match them with the image.
174
+ - Tools
175
+ - [PeakVisor](https://peakvisor.com/)
176
+ - [Peakfinder](https://www.peakfinder.org/)
177
+ - [PeakLens](https://peaklens.com/) AR mountain identifier
178
+ - Methodology
179
+ - Align the silhouette of mountains in the image with the 3D models in the tools.
180
+ - Adjust parameters like viewing angle and elevation.
181
+
182
+ ### Fire Identification
183
+
184
+ - Identify fires, deforestation, or environmental changes.
185
+ - Tools
186
+ - [NASA FIRMS](https://earthdata.nasa.gov/earth-observation-data/near-real-time/firms)
187
+ - [Sentinel Hub Playground](https://apps.sentinel-hub.com/sentinel-playground/)
188
+ - [Global Forest Watch](https://www.globalforestwatch.org/)
189
+ - [Copernicus EFFIS](https://effis.jrc.ec.europa.eu/) EU wildfire monitoring portal
190
+
191
+ ### Track and Find Planes
192
+
193
+ - Use [Apollo Hunter](https://imagehunter.apollomapping.com/) to find exact satellite image time
194
+ - Then use [FlightRadar](https://www.flightradar24.com/) to track that plane that you found
195
+ - Verify the size and plane features
196
+ - [ADS-B Exchange](https://www.adsbexchange.com/) – unfiltered global flight data
197
+
198
+ ## Video Analysis
199
+
200
+ - Find context regarding the video
201
+ - Signs, banners, and billboards.
202
+ - Architectural styles and building materials.
203
+ - Road markings and traffic signs.
204
+ - License plates
205
+ - Clothing styles and local customs.
206
+ - Search for video snippets on platforms like YouTube, Twitter, or TikTok.
207
+ - Metadata Extraction
208
+ - [YouTube Data Viewer](https://citizenevidence.amnestyusa.org/)
209
+ - ExifTool: Extract metadata from downloaded video files.
210
+ - Platform-Specific Techniques
211
+ - TikTok and Instagram
212
+ - APIs change often; prefer platform exports when available
213
+ - Sample cadence: 1–4 h for fast‑moving topics; keep a fixed persona and capture logs
214
+ - Analyze user profiles for location tags; examine comments and hashtags for clues
215
+ - **Bluesky AT Protocol**
216
+ - Resolve handles via `https://bsky.social/xrpc/com.atproto.identity.resolveHandle?handle=<handle>` to get DID
217
+ - Extract full identity document: `https://plc.directory/<did>` (returns PLC operations, handle history, PDS endpoint)
218
+ - Real-time firehose: Use [Firesky](https://firesky.tv/) for live keyword/hashtag monitoring across entire network
219
+ - Analytics: [SkyView](https://bsky.jazco.dev/) for follower graphs, post engagement, network analysis
220
+ - Archive early: AT Protocol allows post deletion and handle migration; capture DIDs and post CIDs
221
+ - Labelers and moderation: Check user's selected labelers (affects content visibility); different from centralized moderation
222
+ - PDS (Personal Data Server): Users can self-host; identify via DID document to understand data custody
223
+ - **Mastodon / Fediverse**
224
+ - Instance matters: `@user@mastodon.social` vs `@user@infosec.exchange` - different jurisdictions, moderation policies, logging practices
225
+ - WebFinger for discovery: `https://<instance>/.well-known/webfinger?resource=acct:<user>@<instance>` returns ActivityPub actor URL
226
+ - Cross-instance search: [FediSearch](https://fedisearch.skorpil.cz/) aggregates public posts; not all instances are indexed
227
+ - Instance enumeration: [Fediverse Observer](https://fediverse.observer/), [Fediverse.party](https://fediverse.party/) for instance lists, stats, software versions
228
+ - Graph analysis: Follower/following lists are public by default; export via API for network mapping
229
+ - Privacy considerations: Some instances (e.g., Pixelfed, PeerTube) federate differently; check instance software type
230
+ - Archive via API: ActivityPub objects are JSON-LD; capture `id`, `published`, `content`, `attributedTo` fields
231
+ - Deleted content: Federation is asynchronous; deletions may not propagate immediately; check caches and relay instances
232
+ - Auditory Clues
233
+ - Languages or dialects spoken.
234
+ - Background noises (train horns, call to prayer, wildlife).
235
+ - Tools
236
+ - [Audacity](https://www.audacityteam.org/): Audio editing software
237
+ - [Sonic Visualiser](https://www.sonicvisualiser.org/): Visualize audio data
238
+ - [SoundCMD](https://soundcmd.com/) crowd‑sourced sound‑matching engine
239
+ - Methodology
240
+ - Create spectrograms to identify unique sound patterns.
241
+ - Use **Shazam** or **SoundHound** to identify music tracks.
242
+ - Extract Key Frames
243
+ - Use tools like [FFmpeg](https://ffmpeg.org/) or [VLC Media Player](https://www.videolan.org/vlc/) to capture frames.
244
+ - Extract frames at regular intervals or when significant changes occur.
245
+ - Stitch frames together if the camera pans to create a panoramic image.
246
+ - Create a panorama if the camera pans across a scene.
247
+ - Analyze frames using the same techniques as in image geolocation.
248
+ - When possible, obtain the original upload (avoid re‑encodes) to retain metadata and audio clarity.
249
+ - Decode platform snowflakes (e.g., Discord, Twitter/X) to infer server‑side timestamps for events.
250
+ - **Threads by Instagram**: Similar to Instagram API limitations; use web scraping or official exports where available.
251
+ - **Video stabilization**: Use FFmpeg `deshake` or Blender VSE to stabilize panning/shaky footage for better landmark identification.
252
+
253
+ ## Chronolocation and Time Analysis
254
+
255
+ ### Shadow Analysis
256
+
257
+ - Use shadows to estimate the time of day and date when the image or video was captured.
258
+ - Methodology
259
+ - Determine the length and direction of shadows in the image.
260
+ - Identify objects casting the shadows (e.g., poles, buildings).
261
+ - Calculate Sun Position
262
+ - Use the object's height and shadow length to calculate the solar elevation angle.
263
+ - Determine the azimuth (sun's compass direction).
264
+ - Tools
265
+ - [SunCalc](https://www.suncalc.org/)
266
+ - [ShadeMap](https://shademap.app/) – interactive 3‑D shadow simulator
267
+ - Bellingcat **Shadow‑Finder** micro‑tool
268
+ - Input location coordinates.
269
+ - Adjust dates and times to match shadow lengths and directions.
270
+ - **SunCalc.net**: Similar tool with additional features.
271
+ - NOAA Solar Calculator for precise solar angles by date/time.
272
+ - Use UTC consistently across all notes and screenshots.
273
+ - OSM map‑compare sites and EOX Cloudless layers to cross‑check base imagery.
274
+
275
+ ### Astronomical Calculations
276
+
277
+ - For night images, use celestial bodies to determine time and location.
278
+ - Tools
279
+ - [Stellarium](https://stellarium.org/): Planetarium software
280
+ - SkyMap: Mobile app for stargazing.
281
+ - [MoonCalc](https://www.mooncalc.org/)
282
+ - Methodology
283
+ - Identify visible stars, constellations, or the moon phase.
284
+ - Use software to simulate the sky at different times and locations.
285
+ - Match the celestial arrangement in the image to a specific date and time.
286
+
287
+ ### Satellite Imagery Time
288
+
289
+ - Use historical satellite imagery to determine changes over time.
290
+ - Tools
291
+ - **Google Earth Pro**:
292
+ - Use the historical imagery slider to view images from different dates.
293
+ - [Sentinel Hub EO Browser](https://apps.sentinel-hub.com/eo-browser/)
294
+ - Access Sentinel and Landsat data.
295
+ - Create TimeLapse animations.
296
+ - Methodology
297
+ - Enter the location coordinates.
298
+ - Select appropriate satellite datasets (Sentinel-2, Landsat 8).
299
+ - Analyze changes in the environment to narrow down dates.
300
+ - Record coordinates in WKT and hash cached tilesets for reproducibility where feasible.
301
+
302
+ ## Threat Actor Investigation
303
+
304
+ ### Actor‑Centric Workflow
305
+
306
+ - Scoping
307
+ - Define the actor hypothesis (e.g., APT28, APT29, Turla, Sandworm; APT10, APT41, Mustang Panda, Volt Typhoon).
308
+ - Collect seed reports from CERTs and vendors; extract indicators and TTPs.
309
+ - Indicator harvesting
310
+ - Parse IOCs (domains, IPs, hashes, JA3/JA4, user‑agents) from advisories and reports; normalize and de‑duplicate.
311
+ - Validate IOCs with passive DNS, CT logs, sandbox submissions, and open telemetry where possible.
312
+ - Infrastructure mapping
313
+ - Build pivots from CT logs (SANs, issuer, serials), shared hosting, name‑server reuse, registrar accounts, and HTML/page fingerprints.
314
+ - Enrich with ASN/WHOIS history, RPKI/ROA status, geolocation, and hosting provider relationships.
315
+ - Artifact profiling
316
+ - Extract PE/ELF metadata (PDB paths, compile timestamps, Rich headers, resources language, code‑signing certs).
317
+ - Cluster with fuzzy hashes (SSDEEP/TLSH) and identify packers/loaders; search YARA and sandboxes for near‑matches.
318
+ - Social and procurement pivots
319
+ - Pivot on developer handles, code snippets, academic theses, job posts, and procurement records that imply capability or mandate.
320
+ - Falsification and reporting
321
+ - Weigh each linkage (weak/medium/strong); document alternatives; avoid single‑source attribution.
322
+ - Map TTPs to MITRE ATT&CK and cite sources with exact sections/pages.
323
+
324
+ ### Attribution Discipline
325
+
326
+ - Separate capability from intent and sponsorship; avoid mirror‑imaging.
327
+ - Use a rule‑of‑three: require at least three independent weak signals, or one strong + one weak, before asserting linkage.
328
+ - Prefer durable pivots (registrar accounts, code‑signing cert reuse, build path idioms) over ephemeral ones (resolving IPs).
329
+ - Clearly mark uncertainty levels and confidence (e.g., low/medium/high) and distinguish correlation from control.
330
+
331
+ ### Russia‑Specific Pivots
332
+
333
+ - Corporate/people
334
+ - EGRUL/EGRIP extracts (official registry; captcha‑gated) and Rusprofile/Kontur.Focus summaries for entities and directors.
335
+ - Government procurement: `zakupki.gov.ru` (tenders, contractors), regional portals, and grant listings.
336
+ - Job boards (e.g., `hh.ru`) for role requirements, tech stacks, and office locations.
337
+ - Infrastructure
338
+ - RU WHOIS: `whois.tcinet.ru`; check registrar accounts, nserver patterns, and RU‑center usage.
339
+ - Telegram is widely used; analyze channels, admins, cross‑posts, and bot ecosystems.
340
+ - Media/platforms
341
+ - VKontakte, Odnoklassniki, Rutube, and regional news portals; search in Russian and transliterations.
342
+
343
+ ### China‑Specific Pivots
344
+
345
+ - Corporate/people
346
+ - National Enterprise Credit Info System (`gsxt.gov.cn`) for registered entities; cross‑check with Tianyancha/Qichacha (paid/freemium).
347
+ - ICP filings (`beian.miit.gov.cn`) to link domains to legal entities via Unified Social Credit Codes (USCC).
348
+ - Infrastructure
349
+ - CNNIC WHOIS and hosting footprints; common domestic clouds (Aliyun, Tencent Cloud, Huawei Cloud) and registrar patterns.
350
+ - Media/platforms
351
+ - Weibo, WeChat Official Accounts (via `weixin.sogou.com`), Zhihu, Bilibili, Douyin, Xiaohongshu; search in Chinese and Pinyin.
352
+
353
+ ### Infrastructure & Internet Measurement
354
+
355
+ - Map IPs to ASNs (HE BGP Toolkit, RIPEstat, BGPView); observe peering and hosting ecosystems.
356
+ - Check CT logs (crt.sh) for certificate reuse and issuance cadence; pivot on subjects/issuers/serials.
357
+ - Use URLScan and similar crawlers to capture HTML fingerprints, favicons (mmh3), and script hashes for clustering.
358
+ - Monitor DNS over time (SecurityTrails PDNS, DNSDB) for subdomain churn and staging domains.
359
+
360
+ ## People & Social Media Investigation
361
+
362
+ ### Username Enumeration
363
+
364
+ - Tools:
365
+ - [WhatsMyName](https://whatsmyname.app/)
366
+ - [NameCheckup](https://namecheckup.com/)
367
+ - [Sherlock](https://github.com/sherlock-project/sherlock)
368
+
369
+ ### Profile Picture & Face Search
370
+
371
+ - Tools:
372
+ - [PimEyes](https://pimeyes.com/)
373
+ - [Exposing.ai](https://exposing.ai/)
374
+ - Azure Face API (subject to compliance policies)
375
+
376
+ ### Social Graph & Content Analysis
377
+
378
+ - Tools:
379
+ - [Maltego](https://www.maltego.com/)
380
+ - [snscrape](https://github.com/snscrape/snscrape)
381
+ - [SocialBlade](https://socialblade.com/)
382
+ - Bluesky/Mastodon: use instance explorers and handle resolvers; pivot across the Fediverse
383
+
384
+ ## Infrastructure OSINT
385
+
386
+ ### IP & Domain Discovery
387
+
388
+ - Tools:
389
+ - [Shodan](https://www.shodan.io/)
390
+ - [Censys](https://censys.io/)
391
+ - [Onyphe](https://www.onyphe.io/)
392
+ - [DNSDB](https://www.farsightsecurity.com/solutions/dnsdb/)
393
+
394
+ ### Certificate & Passive DNS
395
+
396
+ - Tools:
397
+ - [crt.sh](https://crt.sh/)
398
+ - [SecurityTrails](https://securitytrails.com/)
399
+
400
+ ### Malware & Artifact Analysis Workflow
401
+
402
+ - Static triage
403
+ - Hash (SHA‑256), strings, import tables, PDB path, Rich header, resources; check VT/Malpedia family hints (do not rely solely on AV labels).
404
+ - Dynamic/sandbox
405
+ - Execute in sandboxes (ANY.RUN, Hybrid Analysis, CAPE, Tria.ge) to collect network IOCs, mutexes, file drops, and C2 patterns.
406
+ - Clustering
407
+ - Use SSDEEP/TLSH and YARA matches to find related samples; compare config schemas and protocol quirks.
408
+ - Reporting
409
+ - Normalize IOCs (STIX 2.1 if possible), include ATT&CK technique IDs, and provide reproduction steps.
410
+
411
+ ### Telegram/WeChat Investigation
412
+
413
+ - Telegram
414
+ - Use public analytics (TGStat, Telemetr, Combot) for channel growth, overlaps, and forwarding graphs.
415
+ - Export channels with Telegram Desktop; preserve message IDs, timestamps (UTC), and media hashes.
416
+ - WeChat
417
+ - Search Official Accounts via `weixin.sogou.com`; archive articles (PNG + WARC); capture `__biz` IDs and publisher metadata.
418
+ - Expect link rot and content takedowns—archive early.
419
+
420
+ ## Automation & Case Management
421
+
422
+ - Tools:
423
+ - [Hunchly](https://www.hunch.ly/) (browser evidence capture)
424
+ - [Kasm Workspaces](https://kasmweb.com/) OSINT‑ready workspace images
425
+ - [ArchiveBox](https://archivebox.io/) – self‑hosted web archiver
426
+ - [SingleFileZ](https://github.com/gildas-lormeau/SingleFileZ)
427
+
428
+ ## Synthetic Media Verification
429
+
430
+ - Tools:
431
+ - [Sensity AI](https://sensity.ai/)
432
+ - [Hive Moderation](https://hivemoderation.com/)
433
+ - [Reality Defender](https://realitydefender.com/)
434
+