# inbug-team/InScan

边界打点后的自动化渗透工具

Repository: https://github.com/inbug-team/InScan
Canonical: https://ross.abutalabs.com/products/inscan
Language: Go
License Family: other
Last push: 2021-07-19T09:34:40+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 1971, "days_push": 1871, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1888, forks 351 (observed 2026-08-28T04:05:49.343848+00:00)

## What it is
InScan is a Go-based automated intranet penetration testing tool designed for use after breaching a network boundary. It provides port scanning, service fingerprinting, PoC-based vulnerability verification, credential brute-forcing with generated dictionaries, and visualized multi-level tunnel management through a web interface.

## Use cases
- scan internal networks after gaining initial foothold
- identify live hosts and open ports on intranet subnets
- fingerprint services and CMS platforms on internal systems
- run PoC vulnerability checks against discovered assets
- brute-force weak passwords on internal web login pages
- pivot through multi-layer networks with visual tunnel management
- generate social-engineering password dictionaries from known credentials
- perform privilege escalation checks on Windows hosts

## When to choose
- you need a dependency-free single binary for intranet scanning in restricted environments
- you want integrated port scanning, service identification, and PoC verification in one tool
- you need to pivot across multiple network layers with visual tunnel control
- you are doing authorized red-team or penetration-test engagements on internal networks

## When to avoid
- you need a fully supported tool with an open-source license and active maintenance
- you want external perimeter vulnerability scanning rather than post-breach internal testing
- your use is not authorized security testing - the tool is explicitly for legal security testing only
- you require the unfinished features like web SSH/RDP management or directory scanning, which were still in development

## Facets
- artifact type: application
- maturity: maintenance
- function: security, penetration-testing, vulnerability-scanning, networking, search-engine
- domain: security, penetration-testing, networking, developer-tools
- platform: cross-platform, windows, cli, self-hosted
- tags: internal-network-pentest, port-scanner, pivoting, tunneling, brute-force, poc-framework, red-team, post-exploitation, web-ui, single-binary, linux

## Member repositories
- inbug-team/InScan (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:49.343848+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:13:30.167692+00:00, confidence not recorded.
  - readme: https://github.com/inbug-team/InScan (fetched 2026-08-28T04:05:49.343848+00:00, sha ea8a0647169f)
- Data as of 2026-08-30T08:39:29.467469+00:00.