06ea4eb0c078f3409d209d1bf6b1f6f18beffbe871578a873873df0443a90b32

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
Not identified. Its build does not name it and it matches no library we know.
How it was built
Written in Rust. wasm-bindgen connects it to the page's JavaScript.
What it can do
Its imports reach: cryptography. Judged from the names of its imports.
Where we saw it
On 1 public scan, 2026-10-04.
Findings
Hashing or cipher loops. Leads, not verdicts: legitimate modules show these too.
Size
31.5 KiB
First seen
2026-10-04
Last seen
2026-10-04
Public scans
1
Functions
89
Imports
5
Exports
9
Data segments
10

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

4 Rust crates from crates.io, with the versions it was built with:

Build tools and versions it names:

  • Rust
  • rustc 1.99.0 (b940084d7 2026-09-28)
  • walrus 0.23.3
  • wasm-bindgen 0.2.100 (2405ec2b4)

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.

Hashing and cipher code

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

  • function 7ChaCha20 · its rotation amounts
  • function 12Salsa20 or ChaCha · constants in its code
  • encrypt_request_bodySalsa20 or ChaCha · constants in its code
  • decrypt_response_bodySalsa20 or ChaCha · constants in its code

Decompiled code

89 of 89 functions decompiled to C-like pseudocode; 5 more are imported from the page.

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.

FunctionSizeBlocksComplexityNotes
No functions match.

Sections

Code 89Data 10Elem 1Type 15Table 2Export 9Global 1Import 5Memory 1Function 89custom: producerscustom: target_features

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. 10 segments, 3.7 KiB in all.

02468Segment 0: 1,457 bytes, 5.04 bits per byteSegment 1: 353 bytes, 3.96 bits per byteSegment 2: 105 bytes, 3.06 bits per byteSegment 3: 289 bytes, 4.43 bits per byteSegment 4: 613 bytes, 4.48 bits per byteSegment 5: 73 bytes, 3.39 bits per byteSegment 6: 808 bytes, 4.9 bits per byteSegment 7: 51 bytes, 1.3 bits per byteSegment 8: 22 bytes, 4 bits per byte
data segment encrypted or compressed 7.5 bits per byteHeight: bits per byte. Width: share of all the data.

Imports (5)

Can reach: crypto.

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.

  • wbg.__wbg_getRandomValues_a89d0bf71092134a
  • wbg.__wbg_new_8a6f238a6ece86ea
  • wbg.__wbg_stack_0ed75d68575b0f3c
  • wbg.__wbg_error_7534b8e9a36f1ab4
  • wbg.__wbindgen_init_externref_table

Exports (9)

Scripts that carry or load it

  • www.cabaia.com loads it; the script is minified or bundled.
  • js.yuma.ai loads it; the script is minified or bundled.

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

In our sandbox

  • Produced 11 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: 1 function (common in codecs and captchas)
  • Known hashing or cipher algorithms: ChaCha20, Salsa20 or ChaCha
  • Encrypted or compressed data: none
  • 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.

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.

  • b1eb5e01…355b9f1.1 MiB · first seen 2026-10-08 · 12 functions in common (30% of this module's, 2% of that one's)
  • 1993fe6f…23fb3e548.6 KiB · first seen 2026-10-13 · 10 functions in common (25% of this module's, 4% of that one's)
  • 415a5903…1697438.9 MiB · first seen 2026-10-17 · 10 functions in common (25% of this module's, under 1% of that one's)
  • 41338809…314979794.0 KiB · first seen 2026-10-04 · 9 functions in common (23% of this module's, 2% of that one's)

Seen on 1 public scan

PageTitleSeenHow it got there
www.cabaia.comCabaia | Ingenious backpacks & sustainable accessories2026-10-04Built by a script at run time; Downloaded as a file