1993fe6f44e0e4635384643a3e0c65cb5b98c116d283218dbe2b9989df23fb3e
The file is the module exactly as the page had it. WebAssembly does nothing on its own: it runs only when a script instantiates it. Labels describe what the module contains and are leads, not verdicts.
At a glance
- What it is
- Built from the Rust crate ezjww_wasm.
- How it was built
- Written in Rust. wasm-bindgen connects it to the page's JavaScript.
- What it can do
- None of its imports reaches the network, runs code or changes the page. Judged from the names of its imports.
- Where we saw it
- On 1 public scan, 2026-10-13.
- Findings
- Dense data. Leads, not verdicts: legitimate modules show these too.
- Size
- 548.6 KiB
- First seen
- 2026-10-13
- Last seen
- 2026-10-13
- Public scans
- 1
- Functions
- 400
- Imports
- 14
- Exports
- 17
- Data segments
- 66
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
3 Rust crates from crates.io, with the versions it was built with:
Build tools and versions it names:
- Rust
- rustc 1.98.1 (48a229cea 2026-09-01)
- walrus 0.26.2
- wasm-bindgen 0.2.122 (ddd322514)
Read from text the build left in the module: source paths, build metadata and .NET metadata. Whoever builds a module can change or remove it, so treat it as a hint.
Decompiled code
399 of 400 functions decompiled to C-like pseudocode; 14 more are imported from the page.
- 1 of 400 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.
| Function | Size | Blocks | Complexity | Notes |
|---|---|---|---|---|
| No functions match. | ||||
Sections
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. 66 segments, 152.9 KiB in all. The chart shows 64: the first 64 and every encrypted or compressed one.
- Segment 19: 8,420 bytes at 7.8 bits per byte
- Segment 20: 11,437 bytes at 7.63 bits per byte
- Segment 21: 43,159 bytes at 7.75 bits per byte
- Segment 27: 51,557 bytes at 7.8 bits per byte
- Segment 36: 7,577 bytes at 7.64 bits per byte
- Segment 60: 5,275 bytes at 7.8 bits per byte
Imports (14)
Imports from wbg are wasm-bindgen glue. Each __wbg_… import calls one JavaScript function in the page, and its name says which (__wbg_fetch_… calls fetch). The __wbindgen_… imports are wasm-bindgen's own helpers for strings, errors and memory.
- ./ezjww_wasm_bg.js.__wbg_set_52b1e1eb5bed906a
- ./ezjww_wasm_bg.js.__wbg_set_dca99999bba88a9a
- ./ezjww_wasm_bg.js.__wbg_set_6be42768c690e380
- ./ezjww_wasm_bg.js.__wbg_String_8564e559799eccda
- ./ezjww_wasm_bg.js.__wbg_new_ce1ab61c1c2b300d
- ./ezjww_wasm_bg.js.__wbg_new_d90091b82fdf5b91
- ./ezjww_wasm_bg.js.__wbg_new_622fc80556be2e26
- ./ezjww_wasm_bg.js.__wbg___wbindgen_throw_1506f2235d1bdba0
- ./ezjww_wasm_bg.js.__wbg_Error_ef53bc310eb298a0
- ./ezjww_wasm_bg.js.__wbg___wbindgen_is_string_c236cabd84a4d769
- ./ezjww_wasm_bg.js.__wbindgen_init_externref_table
- ./ezjww_wasm_bg.js.__wbindgen_cast_0000000000000001
- ./ezjww_wasm_bg.js.__wbindgen_cast_0000000000000002
- ./ezjww_wasm_bg.js.__wbindgen_cast_0000000000000003
Exports (17)
Scripts that carry or load it
- A script in the page carries it as text; the script is minified or bundled.
From public scans. A script loads a module when it fetches or compiles it.
In our sandbox
- Produced 6 strings at run time (text not shown).
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: none recognised
- Encrypted or compressed data: 6 blocks, 124.4 KiB (81.4% of its data)
- JavaScript stored inside: none
- Other modules inside: none
- Imports that read browser or page details: none
- 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.
Seen on 1 public scan
| Page | Title | Seen | How it got there |
|---|---|---|---|
| leading-turquoise-kmec8rj7-dpqhycrne3i1.edgeone.dev | JWW差分ビューア | 2026-10-13 | Built by a script at run time; Embedded in a script |