National Cyber Warfare Foundation (NCWF)login

insto for interactive Instagram OSINT with persistent snapshots and Maltego export


0 user ratings
2026-11-17 09:27:23
milo
Red Team (CNA)
"insto

insto is an interactive Instagram OSINT CLI built on the HikerAPI backend, offering a prompt-toolkit REPL, sqlite-backed snapshot/watch/diff workflows, and Maltego CSV export for authorized investigations.








Toolsubzeroid/insto — interactive Instagram OSINT CLI with pluggable HikerAPI and aiograpi backends
CategoryOpen-source intelligence (OSINT) / social media analysis CLI
Primary UseInstagram profile, network, and geo analytics via /dossier, /intersect, /timeline, and /watch, with --json, --csv, and --maltego output
Safe UseIntended for authorized investigations, law-enforcement/pentest reconnaissance with consent or legal basis, and defensive research on publicly available Instagram data
Telemetry NoteDefault HikerAPI path involves no Instagram login session; queries are visible to the API provider and rate-limited, while the optional aiograpi backend carries account-ban risk per docs/backends.md

insto is a Python-based interactive Instagram OSINT CLI from subzeroid, currently sitting at around 110 stars with an MIT license, that structures open-source intelligence collection around two pluggable backends: the hosted HikerAPI service as the default, and an optional logged-in aiograpi mode for data behind Instagram's login wall. The design philosophy is visible immediately in the README: HikerAPI is deliberately positioned as the primary path precisely because it keeps an investigator's personal Instagram account out of scope, which is both an operational-security decision and a risk-reduction one. The tool targets professionals doing authorized social-media investigations who want structured, repeatable, exportable collection rather than ad-hoc scraping.


Architecturally, insto is disciplined in ways most OSINT CLIs are not. It requires Python ≥ 3.11, everything — backends, the facade layer, and commands — is async def, and the project claims strict mypy, ruff-clean code, and 900+ offline tests. Most interesting is the typed drift handling: every mapper raises a structured SchemaDrift(endpoint, missing_field) exception when HikerAPI's documented response fields move, rather than silently producing broken output. For anyone who has maintained scrapers against third-party APIs, this is a genuinely thoughtful reliability choice, because schema drift is the usual failure mode that quietly corrupts OSINT datasets weeks after a tool ships.


The tool exposes two surfaces over a single command grammar. The first is a prompt-toolkit REPL — started with bare insto or insto @user to pre-select a target — featuring tab completion, a slash-command popup the README likens to Slack or Claude Code, a bottom toolbar showing active target, backend, and remaining HikerAPI quota, and six switchable color themes via /theme. The second is a Unix-friendly one-shot mode: insto @user -c runs a single slash-command and exits, with --json - and --csv - writing structured output to stdout and /batch reading targets from stdin. The README's example cat targets.txt | insto -c batch - info --yes illustrates the intended scripting pattern for larger authorized engagements.


The command surface covers standard profile collection — /info, /posts, /followers — but the differentiators are the analytics commands. /where, /place, and /placeposts perform geo OSINT against location-tagged content; /intersect and /mutuals do network analysis across follower graphs; /timeline analyzes posting cadence; and /fans ranks "superfans" using a weighted formula of ❤️ plus three times 💬 engagement across sampled posts. /dossier assembles all of this into a full target package in one invocation. The README's comparison table claims these geo, network, cadence, and superfan capabilities are unique against Osintgram, Toutatis, and Sherlock, and that claim holds up against what those tools actually expose.


What elevates insto above a one-shot scraper is the persistence layer. Registrations and snapshots live in ~/.insto/store.db, an sqlite store that survives REPL exits and restarts. /watch schedules recurring polling (with a five-minute floor), /diff compares snapshots over time, and a dedicated insto watch-daemon executes persisted watches in the foreground. The daemon is carefully engineered: only one REPL or daemon executes watches per store, it prints recovered-watch counts and estimated backend load at startup, accepts Ctrl+C or SIGTERM cleanly, and resumes due watches without overlapping ticks on restart. There's even a watch-service subcommand to install the daemon as a macOS login item without sudo.


Change notification is handled through webhooks: setting INSTO_WATCH_WEBHOOK_URL makes the REPL or watch daemon emit best-effort JSON notifications after persisted profile changes. The security posture here is notably careful — the URL is never persisted to disk, /config reports only configured or disabled rather than the value, one-shot commands never trigger delivery, and HTTP endpoints are accepted only for localhost or loopback addresses, pushing operators toward trusted HTTPS receivers. These are the kinds of small design decisions that signal the author has thought about operational hygiene, not just features.


Configuration goes through an interactive insto setup wizard that writes ~/.insto/config.toml with mode 0600, prompting for backend choice, credentials, output directory, sqlite store path, and an optional proxy. Secrets are read with getpass so they don't echo to the terminal. Token resolution follows a sensible flag > environment (HIKERAPI_TOKEN) > config precedence, and the same applies to proxy settings — both socks5h:// (Tor) and http:// proxies are supported, which matters for investigators who need to control their network exposure. INSTO_HOME and INSTO_BACKEND round out the environment surface, with a fake backend value reserved for the e2e test suite.


Installation is deliberately isolated: uv tool install insto or pipx install insto, because the README explicitly warns that bare pip install insto fails on PEP 668-compliant systems like Homebrew Python, Debian 12+, and Ubuntu 23.04+. The optional logged-in backend installs as an extra — pipx install 'insto[aiograpi]', or pipx inject insto aiograpi on an existing install — and insto setup then offers the hikerapi | aiograpi choice. The README is refreshingly honest about the trade-off, pointing to docs/backends.md for "the account-ban risk on aiograpi"; running a private-API client against a real Instagram account is against platform terms and carries real suspension risk, which is exactly why it's kept off the default path.


The competitive positioning in the README is unusually thorough and fair-minded. It recommends Osintgram for its large established community (noting it gained HikerAPI support via PR #2586 in August 2025), Toutatis for its narrow email-and-phone extraction focus, and Sherlock/Maigret for cross-platform username enumeration — explicitly suggesting pairing Sherlock to find an account and insto to then do Instagram depth. The author also maintains the related aiograpi async private-API library that powers the optional backend, along with curated OSINT tool lists, so this sits within an actively developed ecosystem rather than being a one-off.


From a defender's and compliance standpoint, everything here queries publicly accessible (or explicitly licensed) Instagram data through a commercial API with quota accounting surfaced in the UI — the README demo shows quota, dollar cost, and a rate cap in the toolbar. The RateLimited.retry_after handling via with_retry means the tool respects provider throttling rather than hammering endpoints. The /watch polling floor of five minutes and quota-aware daemon startup messaging further suggest a tool designed for sustainable, low-noise collection. Investigators should still remember that "public data" does not exempt collection from GDPR-style purpose-limitation and platform terms in many jurisdictions.


For authorized practitioners — threat-intelligence analysts tracking impersonation accounts, investigators with legal basis, or researchers studying influence networks — insto's Maltego integration is a practical highlight: --maltego works on any flat-row command, and /dossier --maltego produces per-section CSVs ready to import into a link-analysis graph. Combined with JSON piping for scripted enrichment and the sqlite diff engine for monitoring account changes over time, insto reads less like a toy scraper and more like a small collection platform, and the typed, tested, async codebase makes it one of the more professionally engineered entries in the Instagram OSINT niche.


Worth watching: the tool's HikerAPI dependency is a commercial third-party service (with 100 free trial requests and an affiliate-linked signup), so long-term viability and data-licensing terms ride on that provider. The SchemaDrift machinery should absorb API evolution gracefully, and the 110-star, MIT-licensed, actively documented project shows early but real traction. For teams that need defensible, repeatable Instagram intelligence workflows with export paths into standard analysis tooling, insto is a strong candidate — provided the collection itself stays within authorized and legal bounds.



Official project repository for subzeroid/insto.

Download Tool

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






Source: OffensiveSec
Source Link: https://www.offsecblog.com/2026/11/insto-for-interactive-instagram-osint.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.