npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@accounta/dsh-bounty-hunt

v0.1.0

Published

DeepSeek Harness plugin for bug bounty hunting automation

Readme

DSH Bounty Hunt Plugin

DeepSeek Harness plugin for automated bug bounty hunting workflows.

Features

  • Target Management: Add, track, and scope targets across multiple bounty programs
  • Finding Tracking: Log, verify, and organize security findings
  • IDOR Testing: Dedicated tools for testing insecure direct object reference vulnerabilities
  • Report Generation: Automatic markdown/JSON/HTML report generation
  • Agent Presets: Pre-configured agents for reconnaissance, exploitation, and reporting

Installation

Quick Install (Recommended)

cd ~/bounty-lab/dsh-bounty-hunt
./install.sh

This automatically registers the plugin in your DSH Web profile.

Manual Install

  1. Get the absolute path:
echo ~/bounty-lab/dsh-bounty-hunt
# Output: /home/edslawn/bounty-lab/dsh-bounty-hunt (or your actual path)
  1. Edit ~/.dsh/profiles/web/cordis.patch.yml:
patch:
  - insert:
      - id: bounty-hunt-plugin
        name: /home/edslawn/bounty-lab/dsh-bounty-hunt/src/index.ts
        config:
          enabled: true
  1. Start DSH:
dsh web

Verify Installation

dsh bounty/list-targets
# Should return: { ok: true, targets: [] }

Usage

Add a Target

dsh bounty/add-target \
  --name "Acme Inc" \
  --domain "acme.com" \
  --program "HackerOne" \
  --scope '["*.acme.com","api.acme.com"]' \
  --outOfScope '["test.acme.com"]'

Test IDOR Vulnerability

dsh bounty/test-idor \
  --endpoint "https://api.target.com/submissions/\{id\}" \
  --idParam "id" \
  --authHeader "Bearer YOUR_TOKEN" \
  --testIds '["submission_1","submission_2","submission_3"]'

Log a Finding

dsh bounty/add-finding \
  --targetName "Acme Inc" \
  --severity "critical" \
  --title "SQL Injection in Login Form" \
  --description "The username field is vulnerable to SQL injection" \
  --endpoint "https://acme.com/login" \
  --proof "' OR '1'='1"

Generate Report

dsh bounty/generate-report \
  --targetName "Acme Inc" \
  --format "markdown"

Agent Presets

Recon Agent

Specialized for target enumeration and attack surface discovery:

dsh --preset recon-agent

Capabilities:

  • Add and manage targets
  • Verify scope compliance
  • List active targets

Exploit Agent

Specialized for vulnerability discovery and testing:

dsh --preset exploit-agent

Capabilities:

  • Test IDOR vulnerabilities
  • Log findings with proof
  • Verify reproducibility

Reporting Agent

Specialized for documentation and submission:

dsh --preset reporting-agent

Capabilities:

  • List findings by severity
  • Generate formatted reports
  • Manage submission status

Workflow Example

1. Start with Recon

dsh --preset recon-agent
# Claude> Add target Acme Inc...
# Claude> Verify scope for api.acme.com...

2. Switch to Exploitation

dsh --preset exploit-agent
# Claude> Test IDOR on /api/submissions/{id}...
# Claude> Log critical finding...

3. Generate Report

dsh --preset reporting-agent
# Claude> Generate markdown report for Acme Inc...
# Claude> Summarize findings by severity...

Integration with Bounty-Lab

The plugin integrates with your existing bounty-lab infrastructure:

~/bounty-lab/
├── dsh-bounty-hunt/          # This plugin
├── methodology/              # Your existing methodology docs
├── targets/                  # Your target research
└── nuclei-templates/         # Your custom templates

Future enhancements can bridge:

  • Nuclei template execution
  • Existing exploit PoCs
  • Historical finding data
  • Methodologies and playbooks

Architecture

The plugin uses Cordis' service model:

interface BountyHuntService {
  targets: BountyTarget[]
  findings: Finding[]
  addTarget(target: BountyTarget): void
  addFinding(finding: Finding): void
  verifyFinding(id: string): void
}

All state is maintained in memory during the session. For persistence, hook into ctx.storage to save findings to SQLite.

Extending the Plugin

Add a Custom Tool

ctx.tools.define('bounty/my-custom-scan', {
  description: 'My custom vulnerability scanner',
  parameters: { /* ... */ },
}, async (args) => {
  // Implementation
  return { ok: true, result: 'data' }
})

Add an Agent Preset

Edit dsh-bundle.yml and add to preset-agents:

preset-agents:
  my-agent:
    description: Custom hunting agent
    tools: [bounty/...]
    systemPrompt: >
      Custom instruction...

Known Limitations

  • Current IDOR testing is a framework; actual HTTP testing requires integration with curl/fetch
  • Findings stored in memory only (not persisted between sessions)
  • No platform API integration yet (HackerOne, Intigriti, Bugcrowd)

Roadmap

  • [ ] HTTP client integration (real IDOR testing)
  • [ ] SQLite persistence for findings
  • [ ] Platform API connectors
  • [ ] Nuclei integration
  • [ ] Multi-target orchestration
  • [ ] Automated verification checks
  • [ ] Slack/Discord reporting

Contributing

Open an issue or PR to improve the plugin!