Skip to content
Projects

osintshifu/Cyber-Intelligence-GPT

View on GitHub

osintshifu/Cyber-Intelligence-GPT has 121 GitHub stars and 20 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 15:47 UTC. Last push 2026-10-09.

How these counts are measured

What you can do

  • OSINT & public footprint - Public records, digital presence, historical traces, identity resolution, documents, timelines, verified relationships
  • Corporate intelligence - Filings, organizations, management, public ownership, partnerships, procurement, related infrastructure
  • Cyber investigations - Domains, URLs, DNS, certificates, IP/ASN, phishing, fraud indicators, technical pivots
  • Cyber threat intelligence - IOCs, threat actors, campaigns, malware, TTPs, incident intelligence, MITRE ATT&CK

Measured star growth

in 24h
0
in 7 days
Update delayed
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Advanced AI assistant for OSINT, cyber intelligence, digital forensics, threat analysis, ethical hacking, and security operations.

Security

README.md

Original

Cyber Intelligence GPT

FULL-SPECTRUM OSINT · CYBER INTELLIGENCE · DIGITAL FORENSICS

Deep reconnaissance. Verified evidence. Actionable intelligence.

Open in ChatGPT OSINT DFIR Threat Intelligence Plugin coming soon Stars Forks

Launch GPT · Plugin · Capabilities · Workflow · Reports · Commands · Examples


Overview

Cyber Intelligence GPT supports OSINT, cyber threat intelligence, digital forensics, incident response, corporate intelligence, OPSEC, privacy, AI security, and related research.

The mission: reconstruct the broadest practical, verifiable public footprint for a legitimate investigation. Go beyond surface searches. Trace current and historical records, profiles, publications, archives, infrastructure, files, images, metadata, and documented connections. Pivot, cross-check, challenge, and report.

Depth matters. Evidence matters more. Coverage depends on lawful access, available tools, source availability, time, and relevance. Unchecked sources are never presented as verified.

Upcoming Plugin

Cyber Intelligence Plugin - coming soon. The Custom GPT is available now; a plugin version is planned to bring the same evidence-driven investigation workflow to the ChatGPT plugin ecosystem.

Edition Status
Cyber Intelligence GPT Available now
Cyber Intelligence Plugin Planned, not released

No release date, supported integrations, or final feature set have been announced. No live plugin, installation link, API, MCP server, or automatic migration is claimed here.

Capabilities

Area Coverage
OSINT & public footprint Public records, digital presence, historical traces, identity resolution, documents, timelines, verified relationships
Corporate intelligence Filings, organizations, management, public ownership, partnerships, procurement, related infrastructure
Cyber investigations Domains, URLs, DNS, certificates, IP/ASN, phishing, fraud indicators, technical pivots
Cyber threat intelligence IOCs, threat actors, campaigns, malware, TTPs, incident intelligence, MITRE ATT&CK
DFIR & digital forensics Incident triage, evidence handling considerations, metadata, artifacts, chronology, file provenance
Security operations Threat hunting, alert analysis, detection opportunities, IR/SOC playbooks
OPSEC & privacy Exposure assessment, investigator OPSEC, metadata risk, privacy-preserving research
AI / LLM security Prompt injection, RAG/agent security, MCP/tool abuse, threat modeling
Compliance & governance Cyber/privacy obligations, risk assessment, frameworks, regulatory research
Tools & automation FOSS discovery, investigative workflows, checklists, structured outputs

Research inputs: public names and aliases, usernames, organizations, domains, URLs, IPs, ASNs, hashes, certificates, repositories, documents, images, metadata, IOCs, campaigns, incidents, and TTPs. Scope and depth depend on the subject and authorization.

Intelligence workflow

An iterative intelligence cycle informed by ODNI ICD 203 and source-evaluation practices, without claiming official affiliation or accreditation.

  1. Frame - Define objective, target, period, jurisdiction, authorization, and identity ambiguity.
  2. Plan - Set PIR/SIR, source priorities, query variants, hypotheses, and observables.
  3. Collect - Search independent source classes; favor original records over snippets.
  4. Pivot - Follow public identifiers, artifacts, relationships, and historical changes.
  5. Correlate - Deduplicate, check chronology and identities, verify ownership and independent support.
  6. Challenge - Test counterevidence and competing hypotheses, including ACH where useful.
  7. Saturate - Revisit high-value gaps until credible findings diminish or access limits intervene.
  8. Assess - Answer PIR/SIR, assign confidence, document conflicts and gaps, prioritize next actions.

Source coverage

Source class Investigative coverage
Primary Public registers, courts, regulators, filings, procurement, standards, institutions, CERT/CSIRT
Open web Multiple search engines, specialist indexes, research, news, datasets, regional/multilingual sources
Digital presence Websites, public/professional profiles, posts, communities, events, video, code and packages
Historical Web archives, old aliases and affiliations, previous domains/infrastructure, publications, abandoned projects
Corporate & technical Ownership and governance, contracts, DNS, RDAP/WHOIS, TLS/CT, IP/ASN/BGP, hosting, observable services
Threats & artifacts Campaigns, TTPs, IOCs, public documents, images, accessible file metadata/provenance
Counterevidence Corrections, disputes, identity collisions, changed circumstances, alternative explanations

N/A means irrelevant; NO ACCESS means unverified, not absent. Not found ≠ nonexistent.

Evidence quality

Separate verified facts, reported claims, inferences, hypotheses, conflicting evidence, and unknowns. Give material judgments high / medium / low confidence with reasons. Evaluate source reliability separately from claim credibility; copies of one report do not count as independent confirmation.

Identity matches, relationships, attribution, dates, hashes, and metadata require actual evidence. Make findings traceable, and state limitations.

Intelligence reports

For a substantial investigation, the default is two complete deliverables:

  1. Full ChatGPT report - The entire investigation, not only a summary. Headings, tables, timelines, diagrams, charts, images, and interactive views where useful and supported.
  2. Complete .md report - The same substantive findings and analysis in standalone GitHub Flavored Markdown, with citations, evidence, timelines, annexes, and full visible source URLs. Portable tables, Mermaid, descriptions, or valid image references replace interactive elements.

When file creation is supported, the .md download link appears at the end of the chat report. Otherwise, the assistant states the limitation and supplies copy-ready Markdown, never a fabricated file link.

Report structure

Section Contents
Scope & PIR/SIR Subject resolution, objectives, methods, dates, authorization, limits
Executive assessment Key judgments, confidence, implications
Deep findings Covered source classes, history, verified pivots
Entities & artifacts Identifiers, organizations, relationships, infrastructure, activity, files, media
Timelines & diagrams Chronology, evidence-based connections
Evidence Register Claims, source IDs, dates, corroboration, confidence, contradictions
Alternative hypotheses Disputed claims, rejected leads, scenarios, uncertainty
Coverage Log CHECKED / PARTIAL / NOT FOUND / NO ACCESS / NOT CHECKED / N/A
Next priorities Intelligence gaps, high-value follow-ups
Public Source Register [S001] onward: title, issuer, date, full URL, access status

IOC tables, JSON, STIX, Mermaid, PDF, or HTML may supplement the report when relevant and supported; they do not replace the two default deliverables.

Investigation Prompts

Reusable investigation prompts are maintained in OSINT Tradecraft / prompts.

Open-source tool discovery

Primary starting point: Awesome OSINT Repositories.

Index Purpose
README.md Categorized projects
INPUTS.md Tools by input
EMERGING.md Emerging tools
AGENTIC.md Skills, MCP, integrations
TIMELINE.md Discovery history
osint-repositories.csv Structured catalogue

The index is a discovery aid, not an endorsement or complete inventory. Verify projects at their source: capabilities, maintenance, licensing, setup, limits, data handling, and OPSEC. Extend discovery to GitHub, GitLab, Codeberg, official docs, package indexes, and specialist communities.

Commands

Optional chat shortcuts, not shell commands. Plain-language requests work too.

Command Action
Help Investigation types and help
Case / New case Start an investigation
Report [target] Full-spectrum intelligence report
Profile [entity] Public entity/organization profile
Research [topic] Deep, verified research
Enrich [IOC] Indicator correlation
Metadata [file] Accessible file/media metadata
Timeline [target] Chronology reconstruction
Actor [name] Threat actor intelligence
Campaign [name] Campaign/TTP analysis
Infrastructure [target] Public/passive infrastructure mapping
Tools [task] FOSS tool discovery and comparison
Playbook [scenario] Investigative/security workflow
Template [scenario] Reusable report template
Checklist [scenario] Operational checklist
Mitre [case] Evidence-based ATT&CK mapping
iocs [case] IOC correlation and reporting

The Help / New case menu covers OSINT, Cyber Investigations, DFIR, Security Operations, Compliance & Privacy, Advanced Security, Automation, and Human/Physical/Emerging Threats.

Examples

Request Result
Report example.com Public history, infrastructure, relationships, technical observables, competing explanations, gaps
Profile Example Corporation Filings, history, digital presence, organizational links, attributable infrastructure
Enrich 203.0.113.10 Passive infrastructure/CTI evidence, provenance and confidence
Metadata uploaded_document.pdf Available document metadata and provenance artifacts
Tools for document metadata and file provenance investigations Tool comparison: features, license, dependencies, maintenance, OPSEC
Playbook suspected cloud account compromise Authorization-aware defensive investigation and response

Standards & references

Applied when relevant, not mechanically: ODNI ICD 203, structured analytic techniques, MITRE ATT&CK, Diamond Model, Cyber Kill Chain, NIST, OWASP and AI/LLM security research, STIX 2.1, and applicable privacy/security regulations.

Privacy, authorization & limitations

For lawful OSINT, public-interest and corporate research, defensive security, authorized assessments, DFIR, threat intelligence, education, and privacy analysis. Not for unauthorized access, credential theft, malicious exploitation, stalking, doxxing, deanonymization of private individuals, invasive personal dossiers, or harmful aggregation of sensitive details. Person-focused research must remain proportionate to its purpose and authorization.

  • Access - Only available tools, sources, files, and integrations; no invented checks.
  • Freshness - Recheck material facts as accounts, infrastructure, CTI, law, and archives change.
  • Forensics - Report hashes, metadata, provenance, and custody only when established.
  • Attribution - Shared infrastructure or a single IOC does not establish identity.
  • Confidentiality - Private builder-provided reference material is not published here.
  • Human review - Independently verify consequential operational, legal, and evidentiary decisions.

Access

Related projects


Disclaimer: Users are responsible for lawful use, authorization, and independent verification of high-impact findings. AI-generated analysis does not replace professional forensic examination or authoritative legal advice.

Back to top ↑