BitcoinAbuse Deprecated
Deprecated. No available replacement.
Data Enrichment & Threat Intelligence · BitcoinAbuse Feed (Deprecated) · Feed
Details
| ID | BitcoinAbuse |
|---|---|
| Provider | BitcoinAbuse |
| Category | Data Enrichment & Threat Intelligence |
| From Version | 5.5.0 |
| Docker Image | demisto/python3:3.10.12.63474 |
| Supported Modules | Agentix XSIAM |
README
BitcoinAbuse.com is a public database of bitcoin addresses used by hackers and criminals.
Supported Cortex XSOAR versions: 5.5.0 and later.
Get Your API Key
In order to use Bitcoin Abuse service, you need to get your API key.
The API key is free and can be achieved by doing the following:
- Navigate to https://www.bitcoinabuse.com and click on “Register” on top right corner of your screen.
- Fill in your details (Name, Email, Password, etc…)
- After your account have been set, go to Settings, and click on “API” section.
- Give your API token a name, and click on “Create”, a screen containing your generated API key
will appear.
Configure BitcoinAbuse in Cortex
| Parameter | Description | Required |
|---|---|---|
| feed | Fetch indicators | False |
| api_key | API Key | True |
| insecure | Trust any certificate (not secure) | False |
| proxy | Use system proxy settings | False |
| initial_fetch_interval | First Fetch Time | True |
| feedReputation | Indicator Reputation | False |
| feedReliability | Source Reliability | True |
| feedExpirationPolicy | False | |
| tlp_color | Traffic Light Protocol Color | False |
| feedFetchInterval | Feed Fetch Interval | False |
| feedExpirationInterval | False | |
| feedBypassExclusionList | Bypass exclusion list | False |
| feedTags | Tags | False |
Fetching indicators
Initial Fetch
When configuring an integration instance, you will be required to enter the first fetch parameter which will set the timeframe to pull Indicators in the first fetch, Two options are available:
- 30 Days - Indicators recorded in the last 30 days (updates every Sunday between 2am-3am UTC.)
- Forever - All recorded indicators (updates every 15th of the month between 2am-3am UTC.)
Note:
- Whenever Forever is selected, in order to bring as much data as possible in the first fetch, we merge the Forever CSV together the 30 Days CSV file to avoid missing as much data as possible.
- Restrictions will be that any data reported between Sunday (after 30 Days file update) to the day of the first fetch
will not be fetched
Each fetch after the initial fetch
Each fetch after the initial fetch will return indicators reported on the previous day (updates once a day between 2am-3am UTC). Therefore, fetching more than once a day will not have any effect.
Commands
You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.
bitcoinabuse-report-address
Reports an abuser to Bitcoin Abuse service. ‘abuse_type_other’ field is required when ‘abuse_type’ is other
Base Command
bitcoinabuse-report-address
Input
| Argument Name | Description | Required |
|---|---|---|
| address | Address of the abuser. | Required |
| abuser | Information about the abuser. | Required |
| description | Description of the abuse. | Optional |
| abuse_type | Type of abuse. The “abuse_type_other” field is required when the value of the “abuse_type” field is “other”. Possible values are “ransomware”, “darknet market”, “bitcoin tumber”, “blackmail scam”, “sextortion”, and “other”. Possible values are: ransomware, darknet market, bitcoin tumbler, blackmail scam, sextortion, other. | Required |
| abuse_type_other | Description of the abuse type. The “abuse_type_other” field is required when the value of the “abuse_type” field is “other”. | Optional |
Context Output
There is no context output for this command.
Command Example
!bitcoinabuse-report-address address=abcde12345 abuser=abuser@abuse.net abuse_type="bitcoin tumbler" description="this is a description of the abuse"
Human Readable Output
Bitcoin address abcde12345 by abuse bitcoin user abuser@abuse.net was reported to BitcoinAbuse API
bitcoinabuse-get-indicators
Gets indicators from the feed.
Base Command
bitcoinabuse-get-indicators
Input
| Argument Name | Description | Required |
|---|---|---|
| limit | The maximum number of results to return. Default is 50. | Optional |
Context Output
There is no context output for this command.
Command Example
!bitcoinabuse-get-indicators limit=1
Context Example
{}
Human Readable Output
Indicators
value type fields bitcoin:1MfhfDZdv2QXmBBZMom5ZnZzp8VVrJUENw Cryptocurrency Address Value: bitcoin:1MfhfDZdv2QXmBBZMom5ZnZzp8VVrJUENw
rawaddress: 1MfhfDZdv2QXmBBZMom5ZnZzp8VVrJUENw
countryname: Australia
creationdate: 2021-01-17T00:30:36.000000Z
description: I know **** is one of your password on day of hack..
Lets get directly to the point.
Not one person has paid me to check about you.
You do not know me and you’re probably thinking why you are getting this email?
in fact, i actually placed a malware on the adult vids (adult porn) website and you know what, you visited this site to experience fun (you know what i mean).
When you were viewing videos, your browser started out operating as a RDP having a key logger which provided me with accessibility to your display and web cam.
immediately after that, my malware obtained every one of your contacts from your Messenger, FB, as well as email account.
after that i created a double-screen video. 1st part shows the video you were viewing (you have a nice taste omg), and 2nd part displays the recording of your cam, and its you.
Best solution would be to pay me $2763.
We are going to refer to it as a donation. in this situation, i most certainly will without delay remove your video.
Bitcoin address: 1MfhfDZdv2QXmBBZMom5ZnZzp8VVrJUENw
[case SeNSiTiVe, copy & paste it]
You could go on your life like this never happened and you will not ever hear back again from me.
You’ll make the payment via Bitcoin (if you do not know this, search ‘how to buy bitcoin’ in Google).
if you are planning on going to the law, surely, this e-mail can not be traced back to me, because it’s hacked too.
I have taken care of my actions. i am not looking to ask you for a lot, i simply want to be paid.
if i do not receive the bitcoin;, i definitely will send out your video recording to all of your contacts including friends and family, co-workers, and so on.
Nevertheless, if i do get paid, i will destroy the recording immediately.
If you need proof, reply with Yeah then i will send out your video recording to your 8 friends.
it’s a nonnegotiable offer and thus please don’t waste mine time & yours by replying to this message.
abusetype: ransomware
tags:
reportscount: 1
cryptocurrencyaddresstype: bitcoin
Configuration parameters
feed— Fetch indicatorsapi_key— API Keycredentials_api_key—insecure— Trust any certificate (not secure)proxy— Use system proxy settingsinitial_fetch_interval— First Fetch Time (required)feedReputation— Indicator ReputationfeedReliability— Source Reliability (required)feedExpirationPolicy—tlp_color— Traffic Light Protocol ColorfeedFetchInterval— Feed Fetch IntervalfeedExpirationInterval—feedBypassExclusionList— Bypass exclusion listfeedTags— Tags
Commands (2)
-
bitcoinabuse-get-indicatorsDeprecatedGets indicators from the feed.
-
bitcoinabuse-report-addressDeprecatedReports an abuser to Bitcoin Abuse service. 'abuse_type_other' field is required when 'abuse_type' is other
category: Data Enrichment & Threat Intelligence provider: BitcoinAbuse commonfields: id: BitcoinAbuse version: -1 configuration: - display: Fetch indicators name: feed type: 8 defaultvalue: 'true' required: false - display: API Key name: api_key type: 4 hidden: true required: false - displaypassword: API Key name: credentials_api_key hiddenusername: true type: 9 required: false - display: Trust any certificate (not secure) name: insecure type: 8 required: false - display: Use system proxy settings name: proxy type: 8 required: false - additionalinfo: The time window for the first fetch (retroactive). defaultvalue: 30 Days display: First Fetch Time name: initial_fetch_interval options: - 30 Days - Forever required: true type: 15 - additionalinfo: Indicators from this integration instance will be marked with this reputation defaultvalue: Bad display: Indicator Reputation name: feedReputation options: - None - Good - Suspicious - Bad type: 18 required: false - additionalinfo: Reliability of the source providing the intelligence data defaultvalue: A - Completely reliable display: Source Reliability name: feedReliability options: - A - Completely reliable - B - Usually reliable - C - Fairly reliable - D - Not usually reliable - E - Unreliable - F - Reliability cannot be judged required: true type: 15 - defaultvalue: indicatorType display: '' name: feedExpirationPolicy options: - never - interval - indicatorType - suddenDeath type: 17 required: false - additionalinfo: The Traffic Light Protocol (TLP) designation to apply to indicators fetched from the feed display: Traffic Light Protocol Color name: tlp_color options: - RED - AMBER - GREEN - WHITE type: 15 required: false - defaultvalue: '1440' display: Feed Fetch Interval name: feedFetchInterval type: 19 required: false - display: '' name: feedExpirationInterval type: 1 required: false - additionalinfo: When selected, the exclusion list is ignored for indicators from this feed. This means that if an indicator from this feed is on the exclusion list, the indicator might still be added to the system. display: Bypass exclusion list name: feedBypassExclusionList type: 8 required: false - additionalinfo: Supports CSV values. display: Tags name: feedTags type: 0 required: false description: Deprecated. No available replacement. display: BitcoinAbuse Feed (Deprecated) name: BitcoinAbuse script: commands: - arguments: - description: Address of the abuser. name: address required: true - description: Information about the abuser. name: abuser required: true - description: Description of the abuse. name: description - auto: PREDEFINED description: Type of abuse. The "abuse_type_other" field is required when the value of the "abuse_type" field is "other". Possible values are "ransomware", "darknet market", "bitcoin tumber", "blackmail scam", "sextortion", and "other" name: abuse_type predefined: - ransomware - darknet market - bitcoin tumbler - blackmail scam - sextortion - other required: true - description: Description of the abuse type. The "abuse_type_other" field is required when the value of the "abuse_type" field is "other". name: abuse_type_other description: Reports an abuser to Bitcoin Abuse service. 'abuse_type_other' field is required when 'abuse_type' is other name: bitcoinabuse-report-address deprecated: true - arguments: - defaultValue: "50" description: The maximum number of results to return. name: limit description: Gets indicators from the feed. name: bitcoinabuse-get-indicators deprecated: true dockerimage: demisto/python3:3.10.12.63474 feed: true isFetchSamples: true script: '' subtype: python3 type: python fromversion: 5.5.0 tests: - No tests (deprecated) deprecated: true