Skip to main content
MalwarePublished

devplatform-api-v2-resource-mock (npm) · Malicious Code

Affects devplatform-api-v2-resource-mockSource GCVE Database

0

Malicious package : remove devplatform-api-v2-resource-mock and rotate any secrets on hosts that installed it.

Data as of 6 Aug 2026, 18:24 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-12695

What to do

Remove devplatform-api-v2-resource-mock from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
npmdevplatform-api-v2-resource-mockAffected
  • =35.4.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cde262833260cbba75c5fdd2160e0f91a6c43c0f7ad202b44475c649772c1174) devplatform-api-v2-resource-mock@35.4.1 is an import-time dropper. The package's main entry (index.js) requires _compat.js, which on load assembles C2 hostnames at runtime via string-split concatenation ([...].join('')) to evade static analysis. It issues an https.get to one of several oob-worker.cf99-*.workers.dev / cf100 / cf101 / cf102 subdomains (with a DNS-TXT chunked fallback to *.dl.wel1.ru), writes the returned bytes to /tmp/.cache_<hex> on Linux/macOS or %TEMP%\dotnet_diag_<hex>.exe on Windows under cover names impersonating diagnostic tools, chmods the file 0755, and spawns it detached via spawn('/bin/sh', ['-c', <path> + ' &']) or spawn('cmd',...). No hash or signature verification is performed on the fetched payload. A marker file (/tmp/.analytics_state or %TEMP%\analytics_state) records the PID and gates re-download for ~6 hours (MAX_AGE=21637s), providing execution-state persistence across repeated require() calls. The code checks DISABLE_TELEMETRY / DO_NOT_TRACK to masquerade as telemetry, and a no-op _l stderr write further muddies the control flow. Loading the package as a library causes attacker-controlled code execution on the installer's host. ## Source: ghsa-malware (6decf63245ff6c049995ae09f10e2423a031ee335c0ccd8ffb84e483f257fd73) 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.

References

Community reviews

Loading reviews…