a2dd89bf4bb66a0460b8167c0d80a5ded151581d0d3ee83e6b19665f60e7a898
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.
- Names it came with
- File name: meetingsui-lbn-vfcpmpu-loadaudioanalyzer. Its build and the addresses it came from say so; whoever builds a module chooses these, so they are hints.
- How it was built
- Compiled with Emscripten, usually from C or C++.
- 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-06.
- Findings
- Hashing or cipher loops. Leads, not verdicts: legitimate modules show these too.
- Size
- 290.8 KiB
- First seen
- 2026-10-06
- Last seen
- 2026-10-06
- Public scans
- 1
- Functions
- 458
- Imports
- 19
- Exports
- 78
- Data segments
- 72
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.
- Optimized after compiling
- wasm-optAn optimizer. It makes the module smaller and faster, and often removes function names.
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.
Decompiled code
458 of 458 functions decompiled to C-like pseudocode; 19 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.
| Function | Size | Blocks | Complexity | Notes |
|---|---|---|---|---|
| No functions match. | ||||
File layout
WebAssembly binary format version 1, core module, 11 sections.
| Section | Offset | Size | Items |
|---|---|---|---|
| type | 0x8 | 325 bytes | 48 |
| import | 0x14d | 117 bytes | 19 |
| function | 0x1c2 | 463 bytes | 458 |
| table | 0x391 | 9 bytes | 1 |
| memory | 0x39a | 8 bytes | 1 |
| global | 0x3a2 | 258 bytes | 37 |
| export | 0x4a4 | 398 bytes | 78 |
| element | 0x632 | 465 bytes | 1 |
| datacount | 0x803 | 3 bytes | |
| code | 0x806 | 218.3 KiB | 458 |
| data | 0x37166 | 70.5 KiB | 72 |
- Memory
- 259 pages (16.2 MiB), up to 259 pages (16.2 MiB)
- Table
- 247 entries, up to 247 entries, funcref
- Globals
- 37
- Element segments
- 1
- Declared data segments
- 72
- 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. 72 segments, 69.9 KiB in all. The chart shows 64: the first 64 and every encrypted or compressed one.
Imports (19)
- a.a
- a.b
- a.c
- a.d
- a.e
- a.f
- a.g
- a.h
- a.i
- a.j
- a.k
- a.l
- a.m
- a.n
- a.o
- a.p
- a.q
- a.r
- a.s
Exports (78)
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 |
|---|---|
| a.a | emscripten::memory_view<char> |
| a.a | emscripten::memory_view<signed char> |
| a.a | emscripten::memory_view<unsigned char> |
| a.a | emscripten::memory_view<short> |
| a.a | emscripten::memory_view<unsigned short> |
| a.a | emscripten::memory_view<int> |
| a.a | emscripten::memory_view<unsigned int> |
| a.a | emscripten::memory_view<long> |
| a.a | emscripten::memory_view<unsigned long> |
| a.a | emscripten::memory_view<int8_t> |
| a.a | emscripten::memory_view<uint8_t> |
| a.a | emscripten::memory_view<int16_t> |
| a.a | emscripten::memory_view<uint16_t> |
| a.a | emscripten::memory_view<int32_t> |
| a.a | emscripten::memory_view<uint32_t> |
| a.a | emscripten::memory_view<int64_t> |
| a.a | emscripten::memory_view<uint64_t> |
| a.a | emscripten::memory_view<float> |
| a.a | emscripten::memory_view<double> |
| a.b | unsigned char |
| a.b | unsigned short |
| a.b | unsi |
| a.b | long |
| a.d | std::wstring |
| a.d | std::u16string |
| a.d | std::u32string |
| a.e | floa |
| a.e | double |
| a.m | void |
| a.n | std::string |
Showing 30 of 31.
In our sandbox
- Produced 3 strings at run time, listed below.
- Ran a long busy loop (often hashing).
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.
- render_activity
- //javascript/apps/realtime/media/audio/wasm_metrics:audio_analyzer_cc
- blaze-out/wasm-opt-ST-bf65b54c902a/bin/javascript/apps/realtime/media/audio/wasm_metrics/audio_analyzer_cc
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: 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 |
|---|---|---|---|
| meet.google.com | Meet - taz-tbkr-dmw | 2026-10-06 | Downloaded as a file |