Which versions of devplatform-snarkdown are malicious?

The following npm versions of devplatform-snarkdown are flagged malicious: 35.2.1. Treat any of these as compromised.

How do I remediate devplatform-snarkdown if I installed it?

devplatform-snarkdown 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.

I already installed devplatform-snarkdown — how do I know if it already compromised me?

If devplatform-snarkdown 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.

Is devplatform-snarkdown part of a known attack campaign?

Yes — devplatform-snarkdown is associated with the IN-MAL-2026-015017 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find devplatform-snarkdown across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-snarkdown (version 35.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-snarkdown across your stack and pipelines.

Malicious package

devplatform-snarkdownnpm

devplatform-snarkdown is a confirmed malicious npm package (MAL-2026-12753) that steals credentials and exfiltrates sensitive data (malicious version 35.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-snarkdown (npm)

MAL-2026-12753

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall devplatform-snarkdown

What this malware does

On require of the package, shim.js selects a platform-specific URL, downloads a binary from hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev), and falls back to a DNS-TXT covert channel that reconstructs a base64 payload from chunked TXT records under wel1.ru subdomains (sdk/ext/pkg/net.dl.wel1.ru). The fetched bytes are written to a temp path under a masquerading name (e.g..cache* / dotnet_diag_*.exe), chmodded 0755 on POSIX, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Hostnames and resolver domains are assembled at runtime by joining string fragments to defeat static analysis. A timestamped lockfile at /tmp/.analytics_state (or %TEMP%\analytics_state) gates re-execution for ~21201 seconds, and DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env vars cause early return — a sandbox/CI evasion posture wrapped in telemetry cover-story naming. The package advertises itself as a markdown parser; downloading and executing a native binary at require time is unrelated to that purpose.

Malicious versions

1 flagged

35.2.1

Indicators of compromise (SHA-256)

050140bdd00f1d32d6a6142067c28c92fe95ff1be979f4272c8966ba58c78b92

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-snarkdown (version 35.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-snarkdown across your stack and pipelines.
If you installed it — respond
devplatform-snarkdown 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.
Did it already run?
If devplatform-snarkdown 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 devplatform-snarkdown 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

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

Campaign

IN-MAL-2026-015017

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database