# @esbuild/android-x64@0.24.2 security report (npm)

- Verdict: **Needs review** (risk level: medium)
- Scanned: 2026-10-04T16:06:09.000Z
- Files reviewed: 2
- Findings: 4 low severity findings
- Report: https://security.togoder.click/npm/@esbuild/android-x64@0.24.2
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## Summary

Togoder Security scanned the npm package @esbuild/android-x64@0.24.2 on Oct 4, 2026. An AI review of 2 source files produced 4 low severity findings. The overall verdict is medium: the findings flag risky but common patterns (dynamic code, unsafe defaults, broad file or network access) rather than confirmed malware.

## Findings

### [low] Expected WebAssembly Runtime Shim

Finding ID: `NPS-9FFE944BBE7D`

File: `wasm_exec.js`

This is the standard, unmodified wasm_exec.js runtime shim from the Go project. It contains no obfuscation, no dynamic eval, no network calls, and no filesystem or process manipulation beyond the intended Go WASM ABI stubs. All 'fs' and 'process' polyfills either buffer console output or return ENOSYS; no external data transmission, credential harvesting, or command execution is present.

### [low] Global scope modification

Finding ID: `NPS-892EBEAC37FD`

File: `wasm_exec_node.js:13`

The script monkey-patches globalThis with Node.js core modules (require, fs, TextEncoder, TextDecoder, performance, crypto). This is standard for the Go WebAssembly shim to expose Node APIs to WASM, but it does modify the global environment.

### [low] Environment variable access

Finding ID: `NPS-1816AE81A213`

File: `wasm_exec_node.js:19`

The script reads and passes the entire process environment (process.env) into the Go WebAssembly runtime. While this is standard for Go's wasm_exec_node.js launcher and necessary to preserve environment variables for the WASM program, it means any secrets present in the environment are accessible to whatever WASM binary is executed. In a legitimate Go toolchain context this is expected behavior, but it constitutes broad environment variable exposure.

### [low] Dynamic code execution via WebAssembly

Finding ID: `NPS-D5C0DDF6E328`

File: `wasm_exec_node.js:21`

WebAssembly.instantiate() loads and executes a WASM binary passed as a command-line argument (process.argv[2]). This is the intended purpose of the Go wasm_exec_node.js shim, but it does execute arbitrary WASM code provided at runtime, which could be a vector if arguments are attacker-controlled.

## Files reviewed

- `wasm_exec_node.js` (medium): The file is the legitimate Go project wasm_exec_node.js launcher; it accesses process.env and executes a WASM binary, but no data exfiltration, credential harvesting, obfuscation, backdoors, or shell spawning is present.
- `wasm_exec.js` (safe): File is the official Go wasm_exec.js runtime shim with no malicious patterns detected; only benign polyfills and WASM ABI glue code are present.

## Version ranges

None of the 2 scanned versions of @esbuild/android-x64 are flagged high or critical. The latest scanned version, 0.28.2, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.

- 0.28.2 (`0.28.2`): clean
- 0.25.8 – 0.28.1 (`>=0.25.8 <=0.28.1`): not scanned
- 0.24.2 (`0.24.2`): medium

## Scanned versions

- [0.28.2](https://security.togoder.click/npm/@esbuild/android-x64@0.28.2): safe, 2026-10-06T14:10:59.000Z
- [0.24.2](https://security.togoder.click/npm/@esbuild/android-x64@0.24.2): medium, 2026-10-04T16:06:09.000Z

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology