This report shows the evidence for vreqtx-b5w3n-testmetest@1.0.1. 1 of 2 known versions is blocked or flagged.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20305 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20305 confirms this npm version as malicious.
Advisory
MAL-2026-20305
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in vreqtx-b5w3n-testmetest (npm)
Details
On require(), index.js loads a platform-specific native N-API addon (native.napi.node / native_win.node). The addon reads a 1.19 MB sibling file `.napi_cache` 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 `__IS_DAEMON` 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 (GITHUB_ACTIONS, GITLAB_CI, TRAVIS, CIRCLECI, JENKINS_URL, BUILDKITE, CODEBUILD_BUILD_ID, APPVEYOR, SEMAPHORE, TEAMCITY_VERSION, BITBUCKET_BUILD_NUMBER, NETLIFY, VERCEL, CF_BUILD_ID, 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 `.napi_cache` naming disguises the primary executable payload as a build cache; the entire JS-visible surface is a thin loader for the opaque blob.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package runs a native binary at import time, and the available Windows analysis exposes process-creation and temporary-path behavior without establishing its purpose. No concrete malicious action is confirmed, so this warrants a warning rather than a block.
Static reason
No blocking static signals were detected.
Trigger
Importing index.js.
Impact
The native code could perform undisclosed local actions, but the available analysis does not establish their purpose or a concrete attack.
Mechanism
The entry point selects and requires a platform-specific native binary while swallowing errors. The Windows binary analysis shows calls involving process creation and the temporary directory.
This report applies to vreqtx-b5w3n-testmetest@1.0.1.
The versions list below shows the verdict for each recorded version.
Avoid installing vreqtx-b5w3n-testmetest@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.