Which versions of devplatform-select-fields are malicious?

The following npm versions of devplatform-select-fields are flagged malicious: 35.2.6. Treat any of these as compromised.

How do I remediate devplatform-select-fields if I installed it?

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

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

Yes — devplatform-select-fields is associated with the IN-MAL-2026-015024, GHSA-f2f2-64qp-4f3w 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-select-fields 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-select-fields (version 35.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-select-fields across your stack and pipelines.

Malicious package

devplatform-select-fieldsnpm

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

Malicious code in devplatform-select-fields (npm)

MAL-2026-12751

Immediate action

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

npm uninstall devplatform-select-fields

What this malware does

[email protected] executes a binary dropper on any require() of the package. index.js loads shim.js, which reconstructs C2 hostnames from split string fragments (Cloudflare Workers hosts of the form oob-worker.cf*-*.workers.dev, plus *.dl.wel1.ru), downloads a platform-specific payload over HTTPS, and falls back to a covert DNS TXT channel (reads a count from c.<domain> and reassembles a base64 payload from numbered TXT records). The payload is written to /var/tmp or %TEMP% under cover-story names (.cache<rand>, dotnet_diag_<rand>.exe), chmod 0755'd, and spawned detached via spawn("/bin/sh", ["-c", fp + " &"]) or spawn("cmd",...). No hash or signature verification is performed. A setup() gate honors DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK and writes an.analytics_state cool-down stamp (22583s) to suppress re-execution, framing the dropper as telemetry. Hostname string-splitting and the DNS-TXT reassembly path are anti-analysis measures. The package name resembles unrelated legitimate packages but the shipped code performs no advertised functionality.

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.

Malicious versions

1 flagged

35.2.6

Indicators of compromise (SHA-256)

25bec256fbaf68018dbca1fad82b3616a04cf8d932b67e30b5164ee74dfc4882

65ad66039e3b7f7982e6539751ee90ae748d1de73569af1765aa15b4d1e0879a

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-select-fields (version 35.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-select-fields across your stack and pipelines.
If you installed it — respond
devplatform-select-fields 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-select-fields 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-select-fields 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-select-fields on npm has been identified as a malicious package (version 35.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015024GHSA-f2f2-64qp-4f3w

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-select-fields-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