WA Modules Loader

A tiny, TypeScript-first toolkit to work with deobfuscated WhatsApp Web modules.

• Minimal Metro-like runtime loader for module files extracted from the bundle
• Register any extra dependency at runtime (sync or async)
• Batteries included shims (Promise, asyncToGeneratorRuntime, err, babelHelpers)
• A small CLI to split a Metro bundle into individual module files

Requires Node.js >= 18

---

Table of Contents

• Install
• Build (repo)
• CLI: Export modules
• Programmatic Export API
• Library: Load and use modules
• Register external modules
• License

---

Install

If you are using this as a dependency in another project:

npm i wa-modules-loader
# or
pnpm add wa-modules-loader
# or
yarn add wa-modules-loader

This repository itself ships compiled code in dist/ when you run the build.

Build (repo)

When working inside this repo:

npm install
npm run build

This compiles TypeScript from src/ to dist/.

---

CLI: Export modules

The CLI splits a Metro bundle into multiple files — one per module occurrence — based on the __d( marker.

# Syntax
wa-export <inputFile.js> <outputDir?>

# Examples (Windows paths)
wa-export C:\path\to\wa-bundle.js C:\path\to\out\deobfuscated

# If <outputDir> is omitted, it defaults to:
# <inputDir>/deobfuscated/<inputNameWithoutExt>

# Export only modules whose names match a regex:
wa-export C:\path\to\wa-bundle.js C:\path\to\out --module-filter "Signal|Crypto"

# You can repeat --module-filter (OR behavior):
wa-export C:\path\to\wa-bundle.js C:\path\to\out --module-filter "/WASignal/i" --module-filter "WACrypto"

--module-filter is regex-based and can be repeated.
Plain values are compiled as case-insensitive regex (new RegExp(value, 'i')), and /pattern/flags keeps the provided flags.

Each file produced still contains the original function wrapper used by Metro. These files are later consumed by the library loader.

Tip: If you are developing locally and want to try the CLI globally, run npm link in the repo. That will make the wa-export command available in your shell.

---

Programmatic Export API

You can also run the exporter from code (without shelling out to the CLI):

import { exportModules } from 'wa-modules-loader'

const result = await exportModules({
    inputFile: 'C:/path/to/wa-bundle.js',
    outputDir: 'C:/path/to/out/deobfuscated',
    mergeCommonNames: true,
    moduleNameFilters: ['WASignal', '/Crypto/i'],
    workers: 4
})

console.log(result)
// {
//   inputFile: 'C:/path/to/wa-bundle.js',
//   outputDir: 'C:/path/to/out/deobfuscated',
//   mode: 'js',
//   bundlesProcessed: 1,
//   filesWritten: 1234,
//   skippedBundles: 0
// }

exportModules() supports .js and .json inputs and uses the same behavior/flags as the CLI (toIa, mergeCommonNames, workers, concurrency, flat/noSubdirs, moduleNameFilters).

---

Library: Load and use modules

The library turns the exported module files back into runnable factories and resolves their dependencies by name (e.g. b("SomeModule"), d("SomeModule")). You are in full control of which modules to load – there is no built-in hardcoded list.

import { ModuleRegistry, registerAll, type ModuleSpec } from 'wa-modules-loader'

async function main() {
    // 1) Prepare your module list (absolute file paths)
    const modules: ModuleSpec[] = [
        { name: 'WASignalKeys', path: 'C:/abs/path/deobfuscated/mMxGWPzRoXp/WASignalKeys.js' },
        {
            name: 'WACryptoPrimitives',
            path: 'C:/abs/path/deobfuscated/mMxGWPzRoXp/WACryptoPrimitives.js'
        }
        // ...add as many as you need
    ]

    // 2) Create a registry and register all modules
    const registry = new ModuleRegistry()
    await registerAll(registry, modules)

    // 3) Resolve and use modules by name
    const WASignalKeys = registry.require<any>('WASignalKeys')
    // ... use WASignalKeys API as needed
}

main().catch(console.error)

What registerAll() provides for you:

• Sets up a few runtime shims commonly expected by the bundle (Promise, asyncToGeneratorRuntime, err, babelHelpers)
• Ensures a WebCrypto implementation is available as globalThis.crypto (via Node’s webcrypto)
• Parses each module file, extracts the function expression, and registers a standardized factory in the registry

Important: Pass absolute file paths in ModuleSpec.path.

---

Register external modules

Sometimes a WA module expects a third-party dependency to be available by name. You can inject these at runtime.

• Sync value (object/function/constant):

registry.registerValue('my-utils', {
    add(a: number, b: number) {
        return a + b
    }
})

• Async loader (e.g., dynamic import):

await registry.registerAsync('tweetnacl', import('tweetnacl'))

// or with a custom loader function
await registry.registerAsync('my-lib', async () => {
    const mod = await import('some-lib')
    return mod // default export is unwrapped automatically if present
})

After registration, these names can be resolved by WA modules using the internal resolver (b("name") / d("name")).

License

MIT