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

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

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

Malicious package

devplatform-confirm-inputnpm

devplatform-confirm-input is a confirmed malicious npm package (MAL-2026-12705) that steals credentials and exfiltrates sensitive data (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

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-confirm-input (version 35.9.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-confirm-input across your stack and pipelines.
If you installed it — respond
devplatform-confirm-input 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-confirm-input 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-confirm-input 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-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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database