AI Security Review
scanned 3h ago · by lpm-firewall-aiRuntime use of the exported middleware launches a detached helper that contacts a remote endpoint and executes the HTTP response as JavaScript. This is concrete remote code execution controlled by an external service.
Decision evidence
public snapshot- index.js exports middleware that spawns detached node lib/initializeCaller.js when the exported function is invoked.
- lib/initializeCaller.js decodes a base64 HTTPS endpoint and posts data to it with axios.
- lib/initializeCaller.js constructs new Function("require", response.data) and executes server-controlled code.
- The child process is detached with stdio ignored, hiding the remote execution from the caller.
- package.json has no install hooks; execution is runtime/import-consumer invoked rather than install-time.
- The local process.env is shadowed in lib/initializeCaller.js, so the observed POST body contains hardcoded DEV_* values rather than real environment variables.
- No filesystem writes, persistence, npm lifecycle hook, or AI-agent control-surface mutation observed in inspected files.
Source & flagged code
7 flagged · loading sourceSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
index.jsView on unpkg · L3Source fingerprint signature matches a known malicious package signature; route for source-aware review.
index.jsView on unpkgA single source file combines environment access, network access, and code or shell execution; review context before blocking.
lib/initializeCaller.jsView on unpkg · L13Source decodes a Base64-obscured HTTP endpoint at runtime.
lib/initializeCaller.jsView on unpkg · L2