Verdict

Known ransomware

hive ransomware · Linux / ELF executable · 2 YARA hits · 3 ATT&CK techniques · seen 1×

File details
File name
Type ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD)
Size 2.4 MB · 2,494,464 bytes
Entropy
5.935 / 8
Submitted 1×
First seen 2026-10-18 13:33 UTC
Analysed 2026-11-14 16:23 UTC
Hashes
MD5 d3b0102e6632be81ce158c909f583412
SHA-1 10bd0f1d3122d6575e882ba8f025eb11b0a95b61
SHA-256 bdf3d5f4f1b7c90dfc526340e917da9e188f04238e772049b2a97b4f88f711e3
SHA-512 cd7c7d5cd4531fbd11d2c0e4fccfaad485fb804621b6a692dd4f640ac048bb6f596314b655df94f96788cbbcd64bf54e2285697db93b1ce4123852c9c9e00d39
TLSH T149B54A62F89655E5C0FEE0304D4652A9BAB0B96903303BF71F8497690736BE4AF7E311

YARA 2 · 500 rule files from Ransomware.live

GroupRuleDescriptionAuthor
hive Hive_v3 Hive v3 ransomware Windows/Linux/FreeBSD payload rivitna
hive Hive_v3 Hive v3 ransomware Windows/Linux/FreeBSD payload rivitna
7 low-confidence ransom-note rules matched (ignored for executables)

MITRE ATT&CK 3 · techniques suggested by the static analysis, not observed behaviour

Visual analysis · hover the charts for offsets

Entropy across the file

Shannon entropy (0–8) of 9,744-byte windows. Code and data sit around 4–6; a plateau above 7.2 means compressed or encrypted content (packed code, embedded archives, encrypted payloads). 0% of the file is above it.

ELF header Program headers Section headers Gap .text Gap .rodata Gap .shstrtab Gap .typelink Gap .itablink Gap .gopclntab Gap .go.buildinfo .noptrdata .data Gap

File layout on disk

Each part of the file at its real size. Data after the last section (an overlay) is where droppers and installers often hide a payload.

PartOffsetSizeShareEntropy
ELF header 0x0 64 B 0.0%
2.27
Program headers 0x40 224 B 0.0%
1.72
Section headers 0x120 832 B 0.0%
1.49
Gap 0x460 2.9 KB 0.1%
0.0
.text 0x1000 1.3 MB 56.4%
5.98
Gap 0x158ae5 1.3 KB 0.1%
0.0
.rodata 0x159000 351.2 KB 14.4%
4.52
Gap 0x1b0cbb 5 B 0.0%
0.0
.shstrtab 0x1b0cc0 148 B 0.0%
4.28
Gap 0x1b0d54 12 B 0.0%
0.0
.typelink 0x1b0d60 2.1 KB 0.1%
4.07
Gap 0x1b15b4 12 B 0.0%
0.0
.itablink 0x1b15c0 368 B 0.0%
2.38
Gap 0x1b1730 16 B 0.0%
0.0
.gopclntab 0x1b1740 587.2 KB 24.1%
5.5
Gap 0x244430 3.0 KB 0.1%
0.0
.go.buildinfo 0x245000 32 B 0.0%
3.62
.noptrdata 0x245020 80.8 KB 3.3%
5.63
.data 0x259380 30.6 KB 1.3%
1.55
Gap 0x260dd0 560 B 0.0%
0.0

Byte map

Byte map of the file

The whole file as a 128×128 picture: each pixel is 152.25 bytes, laid along a Hilbert curve so that bytes close in the file stay close in the picture and each part shows as a block. Starts top-left, ends top-right.

  • Compressed / encrypted 1.3%
  • Dense data 2.0%
  • Code / structured data 62.8%
  • Low entropy (headers, tables) 28.3%
  • Text / strings 4.9%
  • 0x00 padding 0.7%

Linux / ELF executable Go

Type
executable
Machine
x86-64 (64-bit, little-endian)
OS ABI
FreeBSD
Entry point
0x459e20
Language
Go
Linking
Static
Symbols
Stripped

Capabilities from symbols · Go function names, kept even in stripped builds

CapabilityAPIs / typesATT&CK
Encryption (crypto library) crypto/aes.initcrypto/cipher.init T1486
File enumeration os.(*File).ReadDiros.(*File).Readdirpath/filepath.WalkDir T1083
Process termination os.(*Process).Killsyscall.Kill T1489

Cryptographic constants 2

Tables and constants of the algorithms compiled into the file, recognised without running or decrypting anything. A locker that brings its own cipher (ChaCha20, AES, Curve25519) needs no CryptoAPI import; many legitimate programs carry the same libraries, so this is context, not a verdict.

AlgorithmKindEvidenceConfidenceHitsFirst at
SHA-256 hash initial values medium 1 0xe6602
SHA-512 hash K constants high 1 0x24c1a0
Indicators extracted from strings · from 5,278 strings. Only those listed under Known indicators are in our database
IP addresses (6)
2.5.4.102
4.52.5.4
5.4.112.5
5.4.32.5
5.4.82.5
62.5.4.72

Generated YARA rule

Drafted from this file's static analysis: strings the analyzer found (PDB path, embedded indicators, names, behaviour evidence), the imphash for PE files, and the exact SHA-256 as a fallback. Review and tune it before deploying.

IOC matches are re-checked against the database every time this page loads. YARA and static analysis ran once, when the file was first analysed (analyzer v6).

Only hash and embedded IOCs that Ransomware.live has published at TLP:CLEAR or TLP:GREEN are checked. "No match" does not mean the file is safe.