fb9e9cfe8b83a914e40eab2efd3b0d92a61f82a7c968589f223ab2a7e331d314

How it was built

Compiled with Emscripten, usually from C or C++.

Language

C or C++, probablyNot named. Emscripten and clang mostly compile C and C++.

Compiler

EmscriptenThe toolchain that compiles C and C++ (sometimes Rust) for the web. It comes with the JavaScript that loads the module.

System interface

WASIStandard calls for clocks, random numbers and files. In a browser the page's own JavaScript provides them.

Compiler backend

LLVMThe code generator behind rustc, clang, Emscripten and TinyGo.

Read from text inside the module (its build metadata and paths the compiler left) and from its import and export names. Whoever builds a module can change or remove these, so treat them as hints. They say how a module was made, not what it does.

Hashing and cipher code

Algorithms recognised from their published constants, tables and rotation amounts: CRC-32. Legitimate modules use them all the time, for hashing, captchas and encryption, so this is a lead, not a verdict.

Decompiled code

8,337 of 8,342 functions decompiled to C-like pseudocode; 179 more are imported from the page.

• 5 of 8,342 functions could not be decompiled.

Beyond WebAssembly 1.0: Vector (SIMD) instructions (1,281 functions).

Decompiled code is a reconstruction from the file, so names and types are often guesses. Query values in URLs are masked here; the downloaded file is unchanged.

File layout

WebAssembly binary format version 1, core module, 10 sections.

Memory

256 pages (16.0 MiB), up to 32,768 pages (2.0 GiB)

Table

7,532 entries, up to 7,532 entries, funcref

Globals

2

Element segments

1

Function names

none (names were stripped)

Data segments

Each bar is one segment of the module's data: as wide as its size, as tall as its entropy. Bars above the dashed line are encrypted or compressed. 540 segments, 512.6 KiB in all. The chart shows 65: the first 64 and every encrypted or compressed one.

• Segment 147: 8,306 bytes at 7.93 bits per byte

Text it passes to the page

Fixed text the module hands to the page's JavaScript when it calls an import, read from the module file. Imports that reach the network, run code or change the page come first; web addresses are shown as their host.

Showing 30 of 269.

In our sandbox

• Produced 163 strings at run time, listed below.

Checks we ran

• Threat-feed matches: none
• Names of mining software or pools: none
• CryptoNight mining structure: not found
• Hashing or cipher loops: 1 function (common in codecs and captchas)
• Known hashing or cipher algorithms: CRC-32
• Encrypted or compressed data: 1 block, 8.1 KiB (1.6% of its data)
• JavaScript stored inside: none
• Other modules inside: none
• Imports that read browser or page details: 3
• Function names: removed (usual in release builds)

Static checks of the file: nothing in it was run for these. A finding is a lead, not a verdict.

Shares code with

Other modules that contain some of the same functions. They are ranked by functions few modules have, so a language's own runtime does not link every module built with it. Shared code often means a shared library or the same developer. It is a lead, not a verdict.

• 73ab13d9…002c67202.8 KiB · first seen 2026-10-28 · 74 functions in common (2% of this module's, 27% of that one's)
• 991aef74…99a41b605.1 KiB · first seen 2026-10-26 · 34 functions in common (under 1% of this module's, 12% of that one's)
• fa6f6e07…e47ce9141.8 KiB · first seen 2026-10-21 · 32 functions in common (under 1% of this module's, 12% of that one's)
• 06d1ce18…ff89e0164.2 KiB · first seen 2026-10-04 · 7 functions in common (under 1% of this module's, 11% of that one's)
• 0c214988…c901d725.1 KiB · first seen 2026-10-11 · 5 functions in common (under 1% of this module's, 14% of that one's)

Seen on 1 public scan