NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

vreqtx-b5w3n-testmetestnpm

Advisory published Updated

vreqtx-b5w3n-testmetest is a confirmed malicious npm package (MAL-2026-20305) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vreqtx-b5w3n-testmetest (npm)

MAL-2026-20305
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall vreqtx-b5w3n-testmetest

What this malware does

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.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

fd8b0671f1c77b8c7d843dce49845750fd043f50f20c92a4677d1c117b98c00c

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for vreqtx-b5w3n-testmetest (version 1.0.1).

  2. If you installed it — respond

    vreqtx-b5w3n-testmetest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If vreqtx-b5w3n-testmetest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. vreqtx-b5w3n-testmetest on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022955

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks vreqtx-b5w3n-testmetest-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

vreqtx-b5w3n-testmetest (npm) malicious package — MAL-2026-20305 | O3 Security