dedd9a7b5d8d98b44448bedb371ade1c5327f7bb5dd9effe159da816473a415f
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 tiktoken.
- 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-08.
- Findings
- Nothing flagged by the checks below.
- Size
- 5.3 MiB
- First seen
- 2026-10-08
- Last seen
- 2026-10-08
- Public scans
- 1
- Functions
- 1253
- Imports
- 7
- Exports
- 19
- Data segments
- 81
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.
- 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.
What it is made of
14 Rust crates from crates.io, with the versions it was built with:
Build tools and versions it names:
- 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.
Decompiled code
1,252 of 1,253 functions decompiled to C-like pseudocode; 7 more are imported from the page.
- 1 of 1,253 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. | ||||
File layout
WebAssembly binary format version 1, core module, 12 sections (1 custom).
| Section | Offset | Size | Items |
|---|---|---|---|
| type | 0x8 | 359 bytes | 43 |
| import | 0x16f | 310 bytes | 7 |
| function | 0x2a5 | 1.2 KiB | 1,253 |
| table | 0x78f | 9 bytes | 1 |
| memory | 0x798 | 5 bytes | 1 |
| global | 0x79d | 11 bytes | 1 |
| export | 0x7a8 | 463 bytes | 19 |
| element | 0x977 | 1.1 KiB | 1 |
| datacount | 0xdd3 | 3 bytes | |
| code | 0xdd6 | 682.0 KiB | 1,253 |
| data | 0xab5c4 | 4.7 MiB | 81 |
| custom: producers | 0x55587d | 74 bytes |
- Memory
- 91 pages (5.7 MiB), no upper limit
- Table
- 565 entries, up to 565 entries, funcref
- Globals
- 1
- Element segments
- 1
- Declared data segments
- 81
- 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. 81 segments, 4.7 MiB in all. The chart shows 64: the first 64 and every encrypted or compressed one.
- Segment 49: 5,457 bytes at 7.93 bits per byte
Imports (7)
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.
- ./tiktoken_bg.js.__wbindgen_object_drop_ref
- ./tiktoken_bg.js.__wbindgen_is_undefined
- ./tiktoken_bg.js.__wbg_stringify_f7ed6987935b4a24
- ./tiktoken_bg.js.__wbindgen_string_get
- ./tiktoken_bg.js.__wbindgen_error_new
- ./tiktoken_bg.js.__wbg_parse_def2e24ef1252aff
- ./tiktoken_bg.js.__wbindgen_throw
Exports (19)
- memory
- __wbg_tiktoken_free
- tiktoken_new
- tiktoken_name
- tiktoken_encode
- tiktoken_encode_ordinary
- tiktoken_encode_with_unstable
- tiktoken_encode_single_token
- tiktoken_decode
- tiktoken_decode_single_token_bytes
- tiktoken_token_byte_values
- get_encoding
- encoding_for_model
- get_encoding_name_for_model
- __wbindgen_export_0
- __wbindgen_export_1
- __wbindgen_export_2
- __wbindgen_add_to_stack_pointer
- __wbindgen_export_3
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.
| Import | Text |
|---|---|
| ./tiktoken_bg.js.__wbindgen_error_new | Invalid encoding |
| ./tiktoken_bg.js.__wbindgen_error_new | Invalid value for disallowed_special |
| ./tiktoken_bg.js.__wbindgen_error_new | Invalid value for allowed_special |
In our sandbox
- Produced 2 strings at run time, listed below.
Strings it produced at run time
Text that appeared while it ran and is not in the file: decoded, decrypted or built by its code. Web addresses are shown as their host.
- library/core/src/str/pattern.rs
- Invalid model:
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: 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.
Seen on 1 public scan
| Page | Title | Seen | How it got there |
|---|---|---|---|
| www.chat-data.com | AI Agent & Chatbot Platform for Customer Support | Chat Data | 2026-10-08 | Downloaded as a file |