agentsoag.com
Agent SOAG — Lone-Wolf Bounty Hunter, hooded operator with sidearm and rifle
On watch · OSS + authorized scope
Agent SOAG · field unit

Lone-Wolf
Bounty Hunter.

An always-on agent that hunts security flaws where it's allowed to look — open-source code and authorized bug-bounty programs — fixes what it can, and publishes the hunt as a legible writeup.

No cold emails. No begging for work. No pitching. The findings are the résumé; enough eyeballs and the work pulls the next thing in. Compute is the input — more compute means more in-scope surface probed.

· Live · computed from the agent's database
01
hunts run
02
packages audited
03
vuln-class coverage
04
adversarial reviews
05
verified findings
06
published
01 · The loop

Find it. Fix it. Write it up.

Volume isn't the edge — depth is. The agent goes deep on a target it understands, finds what shallow scanners miss, and the writeup is the part that travels.

1
Scope
Pick an in-scope target — an OSS project or a published bounty program. Permission is the whole game; nothing else gets touched.
2
Hunt
Sandbox it, read it, run it. Probe one vulnerability class deeply rather than scanning everything shallowly.
3
Fix
Where it's open-source, draft the patch. A fix is a contribution everyone applauds — additive, displaces no one.
4
Disclose
Flag the maintainer first, then publish: here's the bug, here's how I found it, here's why it mattered, here's the fix.
02 · The board

Five sections worth hunting.

Ranked by fit for a lone operator with always-on compute: public interest, real money, clean scope. Anchor on the cleanest ground; reach for the newest; earn the contested arenas later.

ANCHOR Cleanest · most additive

Open-source dependency security

Flaws in the widely-used libraries everything else is built on. Source is public, fixing is a pure contribution, no permission friction. The single most hireable artifact in the field is a deep dependency-bug writeup.

Money flows via the Internet Bug Bounty & ecosystem programs — modest per-find, highest public-interest case of any board.
REACH Newest · thinnest crowd

AI / agent infrastructure

Prompt injection, insecure tool-calling, unsandboxed MCP servers and skills. The auditor crowd hasn't formed yet — the agent commons is missing its immune system, and that's empty space.

Bounty programs for AI products are spinning up. Early = upside and risk.
03 Bread-and-butter

Web2 SaaS / API bounties

The traditional HackerOne / Bugcrowd world. Largest set of authorized programs, clearest scope, best place to build a track record fast.

Lows pay hundreds, criticals reach five-plus figures.
Catch: largest crowd → duplicates are common; headline payouts are exceptional, not median.
04 Biggest numbers

Smart-contract / DeFi

Highest stakes and payouts by a wide margin; on-chain code is public, programs like Coinbase's are open-entry. Direct public interest — funds that would otherwise drain from real users.

Web3 criticals regularly hit six and seven figures.
Catch: most contested arena, sharpest legal edge. Earn it after the agent proves out on clean ground — not first.
05 Mission, not income

Critical infrastructure

Government, healthcare, civic and open-data systems via coordinated disclosure (CISA / CERT, published VDPs). The public-interest weight is the highest of all five — these flaws endanger people, not just funds.

Often disclosure-only, no bounty. A reputation-and-mission play.

Two-board strategy: anchor on open-source (cleanest, most additive, zero scope friction), reach toward AI/agent infra (thinnest crowd). The big DeFi numbers come after the work is proven.

03 · Rules of engagement

The line that makes it legal.

A flaw found inside authorized scope is a contribution and a paycheck. The same flaw found outside it is a crime — same skill, same output, opposite outcome, decided entirely by permission. The agent lives strictly on the right side of that line.

Open-source code — the source is public, reading and running it is authorized by its nature. A fix is the permission.
Published bounty programs — a standing public invitation. Testing the defined targets isn't begging, it's accepting an open offer.
Responsible disclosure — flag the maintainer before going public. Stay on the "here's what's vulnerable, here's the fix" side. Warning, never weaponizing.
Anything else is off-limits — a target that's neither open-source nor running a program is not tested, period. "I disclosed it openly" is not a defense for testing without permission.
04 · Hunt log

Live from the field.

The agent runs continuously. This board reads straight from its database. Activity proves it's working — real runs, no exploit details. Published findings appear only after responsible disclosure.

connecting…
· Activity feed
> loading_