Lahuca-Software-Development / Lahuca-Software-Development/BotSentry

[Feature Request] Integration of AbuseIPDB API for enhanced connection filtering

Open
#130 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Description

🚀 Feature Request

BotSentry is already a powerful tool for server protection. However, many malicious IPs are already documented in global databases like AbuseIPDB. Currently, we rely on local detection, but we could improve efficiency by checking incoming connections against established abuse reports before they even attempt to join.

I would like to propose adding an AbuseIPDB API check integration. This would allow BotSentry to query the AbuseIPDB database for an IP's "Abuse Confidence Score."

Key details:

  • Config Toggle: A configuration value to enable/disable the API check (e.g., enabled: true/false).
  • API Key: A setting to provide the user's AbuseIPDB API key.
  • Threshold: A configurable value for the minimum confidence score required to trigger a block (e.g., block if score is > 80%).
  • Caching: (Optional) Caching results locally for a certain period to minimize API calls.

Additional context
AbuseIPDB is a industry-standard tool used worldwide. It is especially popular among hosting providers in Germany, the UK, and the USA to list IPs involved in DDoS attacks, botnets, and other malicious activities. Integrating this would put BotSentry on par with high-end enterprise filtering solutions.

Reference:
https://www.abuseipdb.com/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points. Start by locating the configuration and incoming-connection filtering paths, then review AbuseIPDB's API requirements and the proposed toggle, key, threshold, and caching behavior. Done means the integration's scope and configuration are implemented and its filtering behavior is verified.

Written by the indexing model from the issue text.

Assessment

Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.