AbuseIPDB

LAST UPDATED: JUNE 3, 2025

Overview

AbuseIPDB is a project that helps combat hackers, spammers, and online abuse by providing a central repository for reporting and identifying IP addresses linked to malicious activity.

D3 SOAR is providing REST operations to function with AbuseIPDB.

AbuseIPDB is available for use in:

Known Limitations

The API rate limit is based on the account subscription. Users can navigate to User Accounts > Plans on the AbuseIPDB UI to check or change the account plan.

Refer to AbuseIPDB API for detailed information.

Connection

To connect to AbuseIPDB from D3 SOAR, follow this part to collect the required information below:

Configuring AbuseIPDB to Work with D3 SOAR

1. Go to https://www.abuseipdb.com/account.

2. Log into AbuseIPDB with the E-Mail Address and Password.

   

3. On the User Account page, select the API tab, then click the Create Key button.

   

4. Copy and save the API Key. Refer to Step 3J, sub-step 2 in Configuring D3 SOAR to Work with AbuseIPDB.

   

Configuring D3 SOAR to Work with AbuseIPDB

1. Log in to D3 SOAR.

2. Find the AbuseIPDB integration.

   

   1. Navigate to Configuration on the top header menu.

   2. Click on the Integration icon on the left sidebar.

   3. Type AbuseIPDB in the search box to find the integration, then click it to select it.

   4. Click + Connection, on the right side of the Connections section. A new connection window will appear.

3. Configure the following fields to create a connection to AbuseIPDB.

   

   1. Connection Name: The desired name for the connection.

   2. Site: Specifies the site to use the integration connection. Use the drop-down menu to select the site. The Share to Internal Sites option enables all sites defined as internal sites to use the connection. Selecting a specific site will only enable that site to use the connection.

   3. Recipient site for events from connections Shared to Internal Sites: This field is displayed when Share to Internal Sites is selected for the Site field, allowing selection of the internal site for deploying the integration connection.

   4. Agent Name (Optional): Specifies the proxy agent required to build the connection. Use the dropdown menu to select the proxy agent from a list of previously configured proxy agents.

   5. Description (Optional): Add a description for the connection.

   6. Tenant (Optional): When configuring the connection from a master tenant site, users have the option to choose the specific tenant sites to share the connection with. Once this setting is enabled, users can filter and select the desired tenant sites from the dropdowns to share the connection.

      

   7. Configure User Permissions: Defines which users have access to the connection.

   8. Active: Check the checkbox to ensure the connection is available for use.

   9. System Reputation Check: Selecting one or more reputation check tick boxes will run the corresponding check reputation commands under this integration connection to enrich the corresponding artifacts with reputation details.

      For example, an integration connection named "ConnectionA" is configured with the "Sandbox" site. All URL artifacts from the "Sandbox" site will undergo a reputation check using the Check IP Reputation command from that integration. The return data output from this command will then be used to update the risk level of artifacts, which may affect the risk level of incoming events.

      

   10. System: This section contains the parameters defined specifically for the integration. These parameters must be configured to create the integration connection.
       1. Input the Server URL. The default value is https://api.abuseipdb.com.
       2. Input the API Key copied from the AbuseIPDB platform. Refer to Step 4 of Configuring AbuseIPDB to Work with D3 SOAR for more details.
       3. Input the API Version. The default value is v2.

   11. Enable Password Vault: An optional feature that allows users to take the stored credentials from their own password vault. Refer to the password vault connection guide if needed.

   12. Connection Health Check: Periodically checks the connection status by scheduling the Test Connection command at the specified interval (in minutes). Available only for active connections, this feature also allows configuring email notifications for failed attempts.

4. Test the connection.

   

   1. Click on the Test Connection button to verify credentials and connectivity. A success alert displays Passed with a green checkmark. If the connection fails, review the parameters and retry.

   2. Click OK to close the alert window.

   3. Click + Add to create and add the configured connection.

Commands

AbuseIPDB includes the following executable commands for users to set up schedules or create playbook workflows. With the Test Command function, users can execute these commands independently for playbook troubleshooting.

Integration API Note

For more information about the AbuseIPDB API, refer to the AbuseIPDB API reference.

Check IP Reputation

Checks the reputation of specified IP addresses

Input

["***.***.***.***"] 

Output

To view the sample output data for all commands, refer to this article.

D3-defined Risk Levels and Risk Names

The table below lists the possible output risk levels and their corresponding risk names:

Error Handling

If your command fails to execute, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.

Check CIDR Block

Inspects details on the specified network. The details include the netmask of the subnet, the number of hosts the subnet can contain, and the assigned description of the address space.

Input

["***.***.***.***/***"] 

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.

Get Black List

Retrieves a list of the most frequently reported IP addresses, based on AbuseIPDB user-submitted reports.

Input

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data is Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.

Get Categories

Returns a list of category names.

Input

N/A

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data is Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.

Report IP

Submits one or more IP addresses for reporting.

Input

["***.***.***.***", "***.***.***.***"] 

["Frad_Orders","Brute_Force"]

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.

Test Connection

Allows you to perform a health check on an integration connection. You can schedule a periodic health check by selecting Connection Health Check when editing an integration connection.

Input

N/A

Output

Error Handling

If the Return Data is Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.