06d1ce181d580c018a155f7fe64df8b8a06566446cee506ec516eda7d9ff89e0
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
- 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 4 public scans, 2026-10-04 to 2026-10-25.
- Findings
- Dense data. Leads, not verdicts: legitimate modules show these too.
- Size
- 164.2 KiB
- First seen
- 2026-10-04
- Last seen
- 2026-10-25
- Public scans
- 4
- Functions
- 83
- Imports
- 3
- Exports
- 9
- Data segments
- 68
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
83 of 83 functions decompiled to C-like pseudocode; 3 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, 10 sections.
| Section | Offset | Size | Items |
|---|---|---|---|
| type | 0x8 | 140 bytes | 18 |
| import | 0x94 | 21 bytes | 3 |
| function | 0xa9 | 86 bytes | 83 |
| table | 0xff | 7 bytes | 1 |
| memory | 0x106 | 9 bytes | 1 |
| global | 0x10f | 11 bytes | 1 |
| export | 0x11a | 39 bytes | 9 |
| element | 0x141 | 11 bytes | 1 |
| code | 0x14c | 110.0 KiB | 83 |
| data | 0x1b938 | 53.9 KiB | 68 |
- Memory
- 256 pages (16.0 MiB), up to 32,768 pages (2.0 GiB)
- Table
- 4 entries, up to 4 entries, funcref
- Globals
- 1
- Element segments
- 1
- 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. 68 segments, 53.5 KiB in all. The chart shows 64: the first 64 and every encrypted or compressed one.
- Segment 29: 1,586 bytes at 7.6 bits per byte
Scripts that carry or load it
- lite.evernote.com carries it as text; the script is minified or bundled.
- lite.evernote.com 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 2 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.
- N N N N NPF
- 0123456789ABCDEF
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: 1 block, 1.5 KiB (2.9% 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 4 public scans
| Page | Title | Seen | How it got there |
|---|---|---|---|
| accounts.evernote.com | Login to your Evernote account | 2026-10-25 | Base64 text in a script |
| accounts.evernote.com | Login to your Evernote account | 2026-10-18 | Base64 text in a script |
| accounts.evernote.com | Login to your Evernote account | 2026-10-11 | Base64 text in a script |
| accounts.evernote.com | Login to your Evernote account | 2026-10-04 | Base64 text in a script |