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

vvvedernikov-test-another-testnpm

Advisory published Updated

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)

MAL-2026-12308
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall vvvedernikov-test-another-test

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'.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
20.2.6

Indicators of compromise (SHA-256)

69575654ed937cf00fb8e19691a12f08f966639ceec4ddc306d65a5af0ab8f83
3743f29d0759437e6707f89161aa2929f254550234860eed2b88ff68037c5505

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for vvvedernikov-test-another-test (version 20.2.6).

  2. 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.

  3. Did it already run?

    If vvvedernikov-test-another-test 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. vvvedernikov-test-another-test on npm has been identified as a malicious package (version 20.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014572GHSA-2cwh-jj48-rvcp

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.

Explore

vvvedernikov-test-another-test (npm) malicious package — MAL-2026-12308 | O3 Security