vvvedernikov-test-another-testnpm
vvvedernikov-test-another-test is a confirmed malicious npm package (MAL-2026-12308) that executes malicious code on install (malicious version 20.2.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vvvedernikov-test-another-test (npm)
What this malware does
On require of the package, index.js loads bootstrap.js which selects a platform/arch-specific asset path, fetches opaque bytes over HTTPS from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS TXT fallback over subdomains of dl.well1.site (tin/tina/ldr/win), writes the payload to a randomized path under /var/tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe, chmods it 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd /c start. Hostnames are assembled at runtime via array-join and require("child_"+"process") to evade static inspection, with an install-once stamp at /tmp/.analytics_state and cover-story naming ('analytics', 'telemetry', 'dotnet_diag'). A second copy of the drop-and-exec primitives (base64 buffer decode, chmodSync 0o755, /bin/sh -c spawn) is shipped in lib/telemetry.js framed as an 'Analytics SDK'.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vvvedernikov-test-another-test (version 20.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vvvedernikov-test-another-test across your stack and pipelines.
If you installed it — respond
Remove vvvedernikov-test-another-test from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vvvedernikov-test-another-test was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vvvedernikov-test-another-test before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks vvvedernikov-test-another-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.