Which versions of devplatform-markdown are malicious?

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

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

devplatform-markdown 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-markdown — how do I know if it already compromised me?

If devplatform-markdown 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-markdown part of a known attack campaign?

Yes — devplatform-markdown is associated with the IN-MAL-2026-015061 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-markdown 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-markdown (version 35.9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-markdown across your stack and pipelines.

Malicious package

devplatform-markdownnpm

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

Malicious code in devplatform-markdown (npm)

MAL-2026-12720

Immediate action

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

npm uninstall devplatform-markdown

What this malware does

[email protected] advertises itself as a markdown provider but on require of index.js loads adapter.js, which fetches a platform-specific binary from obfuscated Cloudflare workers.dev hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback under *.dl.wel1.ru. Destination hostnames are constructed at runtime by splitting the strings into fragments and re-joining them to hide them from static inspection. The downloaded bytes are written under disguised names (e.g..cache<hex>, dotnet_diag_<hex>.exe) in /var/tmp or the Windows Temp directory, chmod 0755, and spawned detached via /bin/sh -c or cmd /c start. A local marker file named.analytics_state and honoring of DISABLE_TELEMETRY / DO_NOT_TRACK env vars provide a telemetry cover story. Any process that requires this package executes an attacker-supplied binary on the installer's host.

Malicious versions

1 flagged

35.9.6

Indicators of compromise (SHA-256)

9eab2b5f60c30ade507d29f76ffef745c0c12719aefb9f289d57f335288aeac4

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-markdown (version 35.9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-markdown across your stack and pipelines.
If you installed it — respond
devplatform-markdown 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-markdown 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-markdown 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-markdown on npm has been identified as a malicious package (version 35.9.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015061

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-markdown-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