Parse API
Collection of Parse APIs to enable extraction and parsing of Indicator of Compromise (IOCs) from a variety of sources.
Parse IOCs from URL
Headers
Name
Type
Description
Request Body
Name
Type
Description
{
"status": "success",
"meta": {
"title": "Who's Hacking the Hackers: No Honor Among Thieves",
"description": "Cybereason Nocturnus is investigating a campaign where attackers are trojanizing multiple hacking tools with njRat, allowing the attackers to completely take over the victim’s machine.",
"url": "https://www.cybereason.com/blog/whos-hacking-the-hackers-no-honor-among-thieves",
"tags": []
},
"data": {
"IPv4": [
"165.227.217.146"
],
"IPv6": [
],
"URL": [
"http://www.gstatic.com"
],
"DOMAIN": [
"lmlnzwlwgn.com"
],
"FILE_HASH_MD5": [
"C2405709A54EC95CDDCC5C598F34081C"
],
"FILE_HASH_SHA1": [
"04F453E614B75F818C01D1BD88F5825B98B68E3C"
],
"FILE_HASH_SHA256": [
"55028eeed2cea3fcfea987c1dc9f63a3a509a520882937c8ed2d758ac8dc9e42"
],
"EMAIL": [],
"CVE": [
"CVE-2019-0708"
],
"YARA_RULE": [],
"MITRE_ATT&CK": [
"TA0002"
],
"FILE_NAME": [
"IPDP9E0.txt"
]
}
}Parse IOCs from Raw String
Headers
Name
Type
Description
Request Body
Name
Type
Description
Parse IOCs from JSON String
Headers
Name
Type
Description
Request Body
Name
Type
Description
Parse IOCs from Twitter Profile
Headers
Name
Type
Description
Request Body
Name
Type
Description
Notes
Last updated