Which versions of devplatform-confirm-input are malicious?

The following npm versions of devplatform-confirm-input are flagged malicious: 35.9.8. Treat any of these as compromised.

How do I remediate devplatform-confirm-input if I installed it?

devplatform-confirm-input establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If devplatform-confirm-input 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.

Is devplatform-confirm-input part of a known attack campaign?

Yes — devplatform-confirm-input is associated with the IN-MAL-2026-015073 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-confirm-input across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for devplatform-confirm-input (version 35.9.8).

Malicious package

devplatform-confirm-inputnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

devplatform-confirm-input is a confirmed malicious npm package (MAL-2026-12705) that opens a backdoor for remote access (malicious version 35.9.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-confirm-input (npm)

MAL-2026-12705

Immediate action

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

npm uninstall devplatform-confirm-input

What this malware does

[email protected] is advertised as a 'confirm input adapter' but on require() executes ext.js, which fetches a platform-specific binary from string-concatenation-obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), writes it to a temp path disguised as dotnet_diag.exe or a hidden.cache_ file, chmods it 0755, and spawns it detached via cmd.exe or /bin/sh. If HTTPS fails, a DNS-TXT chunked base64 fallback channel over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru retrieves the payload. C2 hostnames and DNS-fallback domains are split into token arrays and reassembled at runtime, and the dropper uses cover-story identifiers ('.analytics_state', 'dotnet_diag_', 'Graceful degradation') to evade static analysis. Installing or importing this package results in remote code execution on the installer's host under attacker-controlled bytes.

Malicious versions

1 flagged

35.9.8

Indicators of compromise (SHA-256)

68424c7a93599d9d6d9391e3236d1ebf1d88fdc590b9c20f1ee615295335e5e8

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for devplatform-confirm-input (version 35.9.8).
If you installed it — respond
devplatform-confirm-input establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If devplatform-confirm-input 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. devplatform-confirm-input on npm has been identified as a malicious package (version 35.9.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015073

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-confirm-input-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database