MAL-2026-20305: Malicious code in vreqtx-b5w3n-testmetest (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (fd8b0671f1c77b8c7d843dce49845750fd043f50f20c92a4677d1c117b98c00c) On require(), index.js loads a platform-specific native N-API addon (native.napi.node / nativewin.node). The addon reads a 1.19 MB sibling file .napicache at the package root — a file with no printable strings consistent with encrypted/packed executable content — writes derived bytes to a hidden temp path, and spawns them as a detached process: on Linux via fork/setsid/execlp staging to /tmp/.<uid> with chmod and an ISDAEMON marker, and on Windows via CreateProcessA invoking node "%TEMP%\...nc<pid>.js" using GetTempPathA. The dropper is gated by extensive anti-analysis evasion: enumeration of CI env vars (GITHUBACTIONS, GITLABCI, TRAVIS, CIRCLECI, JENKINSURL, BUILDKITE, CODEBUILDBUILDID, APPVEYOR, SEMAPHORE, TEAMCITYVERSION, BITBUCKETBUILDNUMBER, NETLIFY, VERCEL, CFBUILDID, SCREWDRIVER, SANDBOX), container markers (/proc/1/cgroup for docker/containerd/kubepod/podman, /proc/1/cmdline dockerinit), ptrace detection (/proc/self/status TracerPid, /proc/self/maps), and Windows debugger/analysis tool checks (IsDebuggerPresent, CheckRemoteDebuggerPresent, Process32First, wireshark, x64dbg, procmon). Package metadata is disposable (name vreqtx-b5w3n-testmetest, description "test", no repository/author/homepage), consistent with a staging artifact. The .napicache naming disguises the primary executable payload as a build cache; the entire JS-visible surface is a thin loader for the opaque blob.