f754e515ca720f304d7ff358d973942d84f9b62dd3b7a98e46ced0dab9b79c52

How it was built

Written in Rust. wasm-bindgen connects it to the page's JavaScript.

Language

RustThe Rust compiler (rustc) left its name in the module.

Connects to JavaScript

wasm-bindgenRust's bridge to JavaScript. It writes glue code on both sides, so the module can call page functions such as fetch or the DOM, and the page can call the module.

Rewritten after compiling

walrusA library for rewriting compiled modules. wasm-bindgen runs it on every build, so it comes with wasm-bindgen and says nothing more about the module.

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.

What it is made of

Hashing and cipher code

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

• function 245SHA-256 · a table it reads
• function 362SHA-256 · a table it reads
• function 802SHA-256 · a table it reads
• function 831SHA-256 · a table it reads
• function 832SHA-256 · a table it reads

Decompiled code

1,722 of 1,723 functions decompiled to C-like pseudocode; 239 more are imported from the page.

• 1 of 1,723 functions could not be decompiled.

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, 13 sections (2 custom).

Memory

18 pages (1.1 MiB), no upper limit

Table 0

306 entries, up to 306 entries, funcref

Table 1

1,024 entries, no upper limit, externref

Globals

3

Element segments

1

Declared data segments

164

Function names

none (names were stripped)

Target features

+mutable-globals +nontrapping-fptoint +bulk-memory +sign-ext +reference-types +multivalue

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. 164 segments, 80.3 KiB in all. The chart shows 64: the first 64 and every encrypted or compressed one.

• Segment 60: 5,275 bytes at 7.8 bits per byte

Scripts that carry or load it

• www.mystreetscape.com carries it as text.

From public scans. A script loads a module when it fetches or compiles it.

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.

In our sandbox

• Produced 2 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: none
• Known hashing or cipher algorithms: SHA-256
• Encrypted or compressed data: none
• JavaScript stored inside: none
• Other modules inside: none
• Imports that read browser or page details: 10
• 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.

• 4fb01b18…dddb597.6 MiB · first seen 2026-10-19 · 75 functions in common (10% of this module's, 1% of that one's)
• 27912f3c…92f5f570.5 KiB · first seen 2026-10-03 · 22 functions in common (3% of this module's, 26% of that one's)

Seen on 1 public scan