MISP Objects

When the leak has been accessible or seen for the last time.

A description of the leak which could include the potential victim(s) or description of the leak.

When the information available in the leak was created. It’s usually before the first-seen.

When the leak has been accessible or seen for the first time.

The link where the leak is (or was) accessible at first-seen.

Type of information leak as discovered and classified by an AIL module.

The AIL sensor uuid where the leak was processed and analysed.

Name of the cookie (if splitted)

Type of cookie and how it’s used in this specific object.

Value of the cookie (if splitted)

Full cookie

A description of the cookie.

Destination ID (victim)

End of the attack

Bits per second

Destination port of the attack

Description of the DDoS

Protocol used for the attack

IP address originating the attack

Beginning of the attack

Packets per second

Port originating the attack

First time the tuple has been seen

Domain name

Last time the tuple has been seen

A description of the tuple

IP Address

Header operating system application binary interface (ABI)

Number of sections

Free text value to attach to the ELF

Address of the entry point

Architecture of the ELF file

Type of ELF

[Insecure] MD5 hash (128 bits)

Secure Hash Algorithm 2 (512 bits)

Free text value to attach to the section

[Insecure] Secure Hash Algorithm 1 (160 bits)

Secure Hash Algorithm 2 (256 bits)

Entropy of the whole section

Secure Hash Algorithm 2 (384 bits)

Secure Hash Algorithm 2 (224 bits)

Size of the section, in bytes

Secure Hash Algorithm 2 (256 bits)

Name of the section

Secure Hash Algorithm 2 (224 bits)

Type of the section

Flag of the section

Fuzzy hash using context triggered piecewise hashes (CTPH)

Attachment

Sender email address

Email address the reply will be sent to

Display name of the sender

X-Mailer generally tells the program that was used to draft and send the original email

Full headers

Identifies a particular conversation thread

Date the email has been sent

Destination email address

Display name of the receiver

Message ID

Subject

MIME Boundary

[Insecure] MD5 hash (128 bits)

Secure Hash Algorithm 2 (512 bits)

Authenticode executable signature hash

Free text value to attach to the file

Entropy of the whole file

[Insecure] Secure Hash Algorithm 1 (160 bits)

Secure Hash Algorithm 2 (384 bits)

The file itself (binary)

Secure Hash Algorithm 2 (256 bits)

Secure Hash Algorithm 2 (224 bits)

Size of the file, in bytes

Pattern that can be found in the file

Fuzzy hash by Trend Micro: Locality Sensitive Hash

Secure Hash Algorithm 2 (256 bits)

Mime type

Secure Hash Algorithm 2 (224 bits)

Filename on disk

Fuzzy hash using context triggered piecewise hashes (CTPH)

City.

The latitude is the decimal value of the latitude in the World Geodetic System 84 (WGS84) reference.

The altitude is the decimal value of the altitude in the World Geodetic System 84 (WGS84) reference.

When the location was seen for the last time.

A generic description of the location.

When the location was seen for the first time.

The longitude is the decimal value of the longitude in the World Geodetic System 84 (WGS84) reference

Region.

Country.

The MIME type of the body of the request

HTTP Request comment

HTTP Basic Authentication Username

The user agent string of the user agent

HTTP Proxy Username

HTTP Method invoked (one of GET, POST, PUT, HEAD, DELETE, OPTIONS, CONNECT)

The domain name of the server

HTTP Proxy Password

HTTP Basic Authentication Password

This is the address of the previous web page from which a link to the currently requested page was followed

An HTTP cookie previously sent by the server with Set-Cookie

Full HTTP Request URL

Request URI

IP Address

Description of the tuple

Last time the tuple has been seen

First time the tuple has been seen

Source port

Destination port

Binary’s name

Number of sections

Type of Mach-O

Free text value to attach to the Mach-O file

Address of the entry point

[Insecure] MD5 hash (128 bits)

Secure Hash Algorithm 2 (512 bits)

Free text value to attach to the section

[Insecure] Secure Hash Algorithm 1 (160 bits)

Secure Hash Algorithm 2 (256 bits)

Entropy of the whole section

Secure Hash Algorithm 2 (384 bits)

Secure Hash Algorithm 2 (224 bits)

Size of the section, in bytes

Secure Hash Algorithm 2 (256 bits)

Name of the section

Secure Hash Algorithm 2 (224 bits)

Fuzzy hash using context triggered piecewise hashes (CTPH)

First time that the unique tuple (rrname, rrtype, rdata) record has been seen via master file import

Resource Record name of the queried resource

Resource Record type as seen by the passive DNS

Resource records of the queried resource

Last time that the unique tuple (rrname, rrtype, rdata) record has been seen via master file import

Best estimate of the apex of the zone where this data is authoritative

How many authoritative DNS answers were received at the Passive DNS Server’s collectors with exactly the given set of values as answers

First time that the unique tuple (rrname, rrtype, rdata) has been seen by the passive DNS

Sensor information where the record was seen

Origin of the Passive DNS response

Last time that the unique tuple (rrname, rrtype, rdata) record has been seen by the passive DNS

Hash (md5) calculated from the import table

Hash of the structural information about a sample. See https://www.usenix.org/legacy/event/leet09/tech/full_papers/wicherski/wicherski_html/

Free text value to attach to the PE

FileDescription in the resources

OriginalFilename in the resources

InternalFilename in the resources

ProductVersion in the resources

CompanyName in the resources

Compilation timestamp defined in the PE header

Lang ID in the resources

ProductName in the resources

Number of sections

Name of the section and position of the section in the PE

Address of the entry point

FileVersion in the resources

Type of PE

Fuzzy Hash (ssdeep) calculated from the import table

LegalCopyright in the resources

[Insecure] MD5 hash (128 bits)

Secure Hash Algorithm 2 (512 bits)

Free text value to attach to the section

[Insecure] Secure Hash Algorithm 1 (160 bits)

Characteristic of the section

Secure Hash Algorithm 2 (256 bits)

Entropy of the whole section

Secure Hash Algorithm 2 (384 bits)

Secure Hash Algorithm 2 (224 bits)

Size of the section, in bytes

Secure Hash Algorithm 2 (256 bits)

Name of the section

Secure Hash Algorithm 2 (224 bits)

Fuzzy hash using context triggered piecewise hashes (CTPH)

A usually unique International Mobile Subscriber Identity (IMSI) is allocated to each mobile subscriber in the GSM/UMTS/EPS system. IMSI can also refer to International Mobile Station Identity in the ITU nomenclature.

Globally Unique Temporary UE Identity (GUTI) is a temporary identification to not reveal the phone (user equipment in 3GPP jargon) composed of GUMMEI and the M-TMSI.

Globally Unique MME Identifier (GUMMEI) is composed from MCC, MNC and MME Identifier (MMEI).

MSISDN (pronounced as /'em es ai es di en/ or misden) is a number uniquely identifying a subscription in a GSM or a UMTS mobile network. Simply put, it is the mapping of the telephone number to the SIM card in a mobile/cellular phone. This abbreviation has a several interpretations, the most common one being Mobile Station International Subscriber Directory Number.

A description of the phone.

When the phone has been accessible or seen for the last time.

Temporary Mobile Subscriber Identities (TMSI) to visiting mobile subscribers can be allocated.

Serial Number.

When the phone has been accessible or seen for the first time.

International Mobile Equipment Identity (IMEI) is a number, usually unique, to identify 3GPP and iDEN mobile phones, as well as some satellite phones.

Amount of dangling strings (string with a code cross reference, that is not within a function. Radare2 failed to detect that function.)

Description of the r2graphity object

Ratio: amount of referenced strings per kilobyte of code section

Amount of referenced strings

Amount of API calls outside of code section (glob var, dynamic API)

Ratio: amount of API calls per kilobyte of code section

Amount of calls to GetProcAddress

Amount of memory allocations

Radare2 commit ID used to generate this object

Graph export in G>raph Modelling Language format

Average size of a callback

Amount of calls to CreateThread

Amount of callbacks (functions started as thread)

Amount of not referenced strings

Amount of API calls inside a code section

Largest callback

Ratio: amount of functions per kilobyte of code section

Amount of API call reference that does not resolve to a function offset

Amount of API calls not ending in a function (Radare2 bug, probalby)

Shortest path to the first time the binary calls CreateThread

Total amount of API calls

Total amount of functions in the file.

Hive used to store the registry key (file on disk)

Registry value type

Name of the registry key

Data stored in the registry key

Full key path

Last time the registry key has been modified

router’s nickname.

router’s publication time. This can be different from first-seen and last-seen.

Tor node comment.

list of flag associated with the node.

When the Tor node designed by the IP address has been seen for the first time.

parsed version of tor, this is None if the relay’s using a new versioning scheme.

Tor node description.

IP address of the Tor node seen.

When the Tor node designed by the IP address has been seen for the last time.

router’s fingerprint.

versioning information reported by the node.

Raw document from the consensus.

Query (after path, preceded by '?')

Port number

First time this URL has been seen

Full hostname

Top-Level Domain

Credential (username, password)

Domain without Top-Level Domain

Fragment identifier is a short string of characters that refers to a resource that is subordinate to another, primary resource.

Last time this URL has been seen

Path (between hostname:port and query)

Full domain

Description of the URL

Full URL

Subdomain

Scheme

Initial publication date

Last modification date

Description of the vulnerability

The vulnerable configuration is described in CPE format

Vulnerability ID (generally CVE, but not necessarely)

Summary of the vulnerability

External references

Initial creation of the whois entry

Expiration of the whois entry

Registar of the whois entry

Full whois entry

Registrant name

Domain of the whois entry

Registrant email address

Registrant phone number

Last update of the whois entry

Certificate invalid before that date

Certificate invalid after that date

Algorithm of the public key

Free text description of hte certificate

[Insecure] Secure Hash Algorithm 1 (160 bits)

Length of the public key (in bits)

Issuer of the certificate

Serial number of the certificate

Version of the certificate

[Insecure] MD5 hash (128 bits)

Exponent of the public key

Subject of the certificate

Secure Hash Algorithm 2 (256 bits)

Modulus of the public key

Raw certificate base64 encoded