ScanMalware.com
WebAssembly module
API
This view is built from:
Module analysis/api/v1/wasm/991aef749d8f6aea8c4bbab98503d279750fefa52e5d58319771ab47da99a41bDecompiled code/api/v1/wasm/991aef749d8f6aea8c4bbab98503d279750fefa52e5d58319771ab47da99a41b/code

991aef749d8f6aea8c4bbab98503d279750fefa52e5d58319771ab47da99a41b

Download .wasmSearch scans with this module

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 front.myshopline.com. 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-26.
Findings
Nothing flagged by the checks below.
Size
605.1 KiB
First seen
2026-10-26
Last seen
2026-10-26
Public scans
1
Functions
533
Imports
3
Exports
33
Data segments
30

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.

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

533 of 533 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.

FunctionSizeBlocksComplexityNotes
No functions match.

File layout

WebAssembly binary format version 1, core module, 10 sections.

SectionOffsetSizeItems
type0x8302 bytes36
import0x13678 bytes3
function0x184538 bytes533
table0x39e9 bytes1
memory0x3a79 bytes1
global0x3b016 bytes2
export0x3c0672 bytes33
element0x660470 bytes1
code0x836584.0 KiB533
data0x9284519.1 KiB30
Memory
256 pages (16.0 MiB), up to 32,768 pages (2.0 GiB)
Table
245 entries, up to 245 entries, funcref
Globals
2
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. 30 segments, 18.9 KiB in all.

02468Segment 0: 869 bytes, 4.5 bits per byteSegment 1: 1,185 bytes, 3.17 bits per byteSegment 2: 9 bytes, 1.45 bits per byteSegment 3: 13 bytes, 1.2 bits per byteSegment 4: 819 bytes, 3.08 bits per byteSegment 5: 81 bytes, 1.79 bits per byteSegment 6: 139 bytes, 1.97 bits per byteSegment 7: 598 bytes, 2.31 bits per byteSegment 8: 263 bytes, 3.12 bits per byteSegment 9: 518 bytes, 2.36 bits per byteSegment 10: 610 bytes, 3.82 bits per byteSegment 11: 2,688 bytes, 1.93 bits per byteSegment 12: 65 bytes, 2.24 bits per byteSegment 13: 33 bytes, 1.91 bits per byteSegment 15: 21 bytes, 1.05 bits per byteSegment 17: 21 bytes, 1.53 bits per byteSegment 19: 30 bytes, 1.53 bits per byteSegment 20: 14 bytes, 1.2 bits per byteSegment 22: 21 bytes, 1.28 bits per byteSegment 24: 127 bytes, 4.74 bits per byteSegment 27: 11,182 bytes, 4.78 bits per byteSegment 28: 2 bytes, 1 bits per byteSegment 29: 5 bytes, 2.32 bits per byte
data segment encrypted or compressed 7.5 bits per byteHeight: bits per byte. Width: share of all the data.

Imports (3)

  • env.emscripten_resize_heap
  • env.emscripten_memcpy_big
  • env.setTempRet0

Exports (33)

Scripts that carry or load it

  • front.myshopline.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 1 string 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.

  1. St9type_info

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.

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.

  • fb9e9cfe…31d3145.9 MiB · first seen 2026-10-21 · 34 functions in common (12% of this module's, under 1% of that one's)

Seen on 1 public scan

PageTitleSeenHow it got there
getphotoblanket.comGetPhotoBlanketUS2026-10-26Base64 text in a script