a255a6ac267921443100294c2efe51f21c326b46a8d5cc331cb436c6f319c4ea
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
- From experience.arcgis.com (2 sites) · File name: pe-wasm. Its build and the addresses it came from say so; whoever builds a module chooses these, so they are hints.
- How it was built
- Not named in the module.
- 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 2 public scans, 2026-10-15 to 2026-10-23.
- Findings
- Dense data. Leads, not verdicts: legitimate modules show these too.
- Size
- 2.7 MiB
- First seen
- 2026-10-15
- Last seen
- 2026-10-23
- Public scans
- 2
- Functions
- 1559
- Imports
- 18
- Exports
- 185
- Data segments
- 26782
Analysis limits
Only its first 2,000 strings were read.
How it was built
The module names no language, compiler or build tool. Release builds often strip this information, and hand-written modules usually lack it.
Decompiled code
1,559 of 1,559 functions decompiled to C-like pseudocode; 18 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 | 635 bytes | 79 |
| import | 0x283 | 111 bytes | 18 |
| function | 0x2f2 | 1.5 KiB | 1,559 |
| table | 0x90e | 9 bytes | 1 |
| memory | 0x917 | 9 bytes | 1 |
| global | 0x920 | 11 bytes | 1 |
| export | 0x92b | 1.1 KiB | 185 |
| element | 0xd60 | 2.1 KiB | 1 |
| datacount | 0x15b8 | 5 bytes | |
| code | 0x15bd | 1020.4 KiB | 1,559 |
| data | 0x100765 | 1.7 MiB | 26,782 |
- Memory
- 159 pages (9.9 MiB), up to 32,768 pages (2.0 GiB)
- Table
- 1,134 entries, up to 1,134 entries, funcref
- Globals
- 1
- Element segments
- 1
- Declared data segments
- 26,782
- 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. 26,782 segments, 1.5 MiB in all. The chart shows 66: the first 64 and every encrypted or compressed one.
- Segment 393: 1,362 bytes at 7.55 bits per byte
- Segment 394: 1,384 bytes at 7.54 bits per byte
Imports (18)
- 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
Exports (185)
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.
- *ABCDEFGH*JKLMNPQR*STUVWXYZ
- JKLPQRSTUXYZABCFGHJKLPQR
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: 2 blocks, 2.7 KiB (0.2% 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 2 public scans
| Page | Title | Seen | How it got there |
|---|---|---|---|
| housing.umn.edu | West Bank Townhouses | Housing & Residential Life | 2026-10-23 | Built by a script at run time |
| www.joincalfire.com | Join CAL FIRE | Join CAL FIRE | 2026-10-15 | Downloaded as a file |