seekr is a Go-based OSINT toolkit that unifies data gathering, note taking, and target databases behind a browser interface, aimed at investigators and authorized researchers.
| Tool | seekr-osint/seekr — a multi-purpose OSINT toolkit with a Go backend, BadgerDB storage, and a web interface |
| Category | OSINT collection and case-management framework |
| Primary Use | Consolidating authorized OSINT workflows: enumerating accounts, linking GitHub identities to emails, and storing per-target records with BadgerDB |
| Safe Use | Intended for legitimate, lawful investigations, authorized assessments, and educational research only; the project explicitly prohibits doxxing and illegal use |
| Telemetry Note | As a client-side aggregation tool, seekr leaves footprints on the third-party services it queries (site requests from your IP) and stores collected data locally in BadgerDB files on the operator's machine |
seekr positions itself as a multi-purpose toolkit for gathering and managing OSINT data, and the emphasis on managing is what separates it from the typical one-shot enumeration script. The project, hosted at seekr-osint/seekr and written in Go with a TypeScript front end, has accumulated roughly 870 stars and is released under GPL-3.0. Rather than forcing an investigator to juggle a dozen terminal windows and scattered notes, seekr binds collection utilities, a target database, and a note-taking layer into a single browser-accessible workspace served on port 8569. The README frames the audience plainly: researchers, investigators, and anyone who needs to gather information in a structured way.
Architecturally, the interesting choice is BadgerDB as the persistence layer. BadgerDB is an embedded key-value store native to the Go ecosystem, which means seekr ships as a single self-contained binary with no external database server to provision. That decision keeps the deployment story simple — download an executable, run it, open the web interface — and it fits the project's self-description as a desktop-style application that happens to live in a browser tab. Everything an operator records about a target, from predefined fields to free-form notes, lands in local files under the operator's control rather than a cloud service.
The feature list in the README reveals the project's philosophy. First, no API keys are required for any feature, which removes the most common friction point in OSINT tooling — credential provisioning and rate-limit headaches before you can even start. Second, seekr explicitly supports integration and adaptation of established OSINT tools, citing phoneinfoga as an example, so it behaves more like a host environment than a monolith. The desktop interface metaphor, implemented with windowing libraries such as WinBox.js, gives each utility its own draggable panel rather than a rigid tab layout.
Two capabilities deserve specific attention. The GitHub-to-email mapping feature, flagged in the repo topics as github-osint, attempts to correlate a GitHub identity with associated email addresses — a classic pivot point in attribution work. Alongside it, the account discovery mechanism feeds directly into what the README calls account cards: per-person records in the database that accumulate discovered identities across platforms. This card model effectively turns ad hoc enumeration into a persistent, queryable case file, which is where the management half of the tool earns its keep.
The guide feature is a quieter but thoughtful addition. An operator enters the information currently in hand, and seekr recommends web-based tools suited to that starting point — a decision-tree style onboarding for people who know their objective but not the tooling landscape. Combined with predefined commonly used fields in the database, it lowers the barrier for analysts who are methodical but not deeply technical. The theming and plugin system suggests the developers intend seekr to grow into an extensible framework rather than a fixed feature set, and the repo topics (osint-framework, osint-toolkit) reinforce that ambition.
Installation paths cover the major platforms. Stable builds are distributed as precompiled binaries for Windows and Linux via the project's GitHub releases, and a Docker image is published at ghcr.io/seekr-osint/seekr:latest, runnable with a single docker run -p 8569:8569 invocation. The unstable build path requires Go and TypeScript installed locally, cloning the repo, running go generate ./..., compiling the web assets with tsc --project web, and launching via go run main.go. There is even first-class NixOS support through nix flakes: nix shell github:seekr-osint/seekr followed by seekr. The README is candid that unstable builds are not production-ready, and the project labels itself beta software still in early development.
From an operational standpoint, treating seekr as a case-management hub alongside your existing tools is the intended posture — the authors state it can be used with, not instead of, your current stack. In an authorized engagement, that means using the database as your single source of truth for findings while individual collection modules run against in-scope, legally permissible targets. The legal disclaimer in the README is unusually explicit: the tool is for legitimate and lawful use only, for educational and research purposes, and specifically calls out doxxing — researching and broadcasting private identifying information without consent — as prohibited and potentially criminal. That framing is worth internalizing, because OSINT tooling sits closest to the line between investigation and harassment of any category in the security toolkit.
Defenders should understand what seekr is not. It is not an exploit framework, does not touch victim infrastructure directly, and generates no attack traffic beyond ordinary requests to public web services and APIs. Its footprint is almost entirely client-side: queries originate from the operator's IP against public sources, and results persist locally in BadgerDB files on the operator's machine. For blue-team awareness, that means the observable artifacts of seekr use appear in the logs of the queried platforms (patterned lookups, user-agent behavior) and on the operator's own filesystem, not on target systems.
Caveats worth weighing: the beta status is real, and the maintainers themselves warn that unstable builds contain bugs. The no-API-keys promise is convenient but implies reliance on unauthenticated endpoints, which can break silently when upstream services change. Contributors credited in the README include WinBox.js and FileSaver.js for the interface plumbing and a discord.go implementation borrowed from the wau project, suggesting at least one Discord-related lookup capability beyond what the feature list spells out. The project wiki holds the setup guide and API documentation for deeper integration work.
For authorized investigators who currently maintain OSINT findings in scattered text files and browser bookmarks, seekr offers a coherent alternative: collection, correlation, and record-keeping in one local workspace with a permissive license and a Docker-friendly footprint. Treat it as promising beta infrastructure — run stable releases, validate findings against primary sources, and keep its legal disclaimer in view — and it can genuinely streamline a lawful OSINT workflow.
seekr-osint/seekr.Educational analysis for authorized security professionals. Use only in controlled, authorized environments.
Related coverage
0 comentários:
Post a Comment
Note: Only a member of this blog may post a comment.