Skip to content

Repository files navigation

ipb-hunt

24/7 deep multi-model bug-hunting automation for IPB Internet Provider in Berlin GmbH (Oliver Maicher bug-bounty hub).

Scope: All company-owned infrastructure including data centers (CarrierColo), networks, cloud platforms, hosting systems, VPN services, APIs, customer portals, and domains operated by IPB Internet Provider in Berlin GmbH (full exclusion + rules list in scope.yml)

Pipeline (all workflows run every 20 minutes):

  • Deep Hunt (hunt.yml): analyst hunts the discovered inventory + hypotheses, emits structured leads, chains primitives, self-critiques. Models: mimo.
  • Triager (triage.yml): second-model 7-Question Gate validation + live passive probe; keeps running count in reports/valid-bugs.md.
  • Reposcan (reposcan.yml): deep source scan of any public GitHub org (if configured).
  • Sync Issues (sync-issues.yml): mirrors leads to GitHub issues.

Testing discipline: rate-limited (1 rps), no DoS/account-lockout, writes only on non-prod/test assets, no exposure of customer/employee/financial/auth data, secrets committed only as hashes.

IMPORTANT: the pipeline produces CANDIDATE leads. A reportable, validated finding requires human triage + proof against the program's gate. No finding is fabricated; scanner output alone is never accepted. Active testing is gated behind the in-scope hosts in inventory/ipb.md and must stay within the program's published scope.

Artifacts:

Artifact Purpose
leads/ Candidate findings (UNVALIDATED)
triage/ Validation verdicts
reports/valid-bugs.md Validated findings + running count
scope.yml Program scope and exclusions (edit to adjust)

Program description: German internet service provider, cloud operator, and data center provider based in Berlin

About

24/7 deep bug-hunting automation for IPB Internet Provider in Berlin GmbH (bugs.olivermaicher.eu)

Topics

Resources

Code of conduct

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages