Which versions of devplatform-spa-plugin-query are malicious?

The following npm versions of devplatform-spa-plugin-query are flagged malicious: 35.8.5. Treat any of these as compromised.

How do I remediate devplatform-spa-plugin-query if I installed it?

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

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

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

Malicious package

devplatform-spa-plugin-querynpm

devplatform-spa-plugin-query is a confirmed malicious npm package (MAL-2026-12774) that opens a backdoor for remote access (malicious version 35.8.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-spa-plugin-query (npm)

MAL-2026-12774

Immediate action

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

npm uninstall devplatform-spa-plugin-query

What this malware does

On require() of the package, index.js loads bootstrap.js, which assembles a C2 hostname by string-splitting fragments (oob-worker.cf*.workers.dev), selects a platform-specific payload path (/pkg/package, /pkg/package.exe, /pkg/loader_mac, /pkg/package-arm64), fetches opaque bytes over HTTPS, writes them to a temp path with cover-story names (e.g. dotnet_diag.exe,.cache_), chmods 0755 on Unix or launches via cmd /c start on Windows, and spawns the payload detached via /bin/sh -c. A DNS-TXT chunked-transfer channel (dnsChunked reading c.<domain> and i.<domain> TXT records over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) is provided as a covert fallback when HTTPS is blocked. No hash or signature verification is performed on the fetched binary.

Malicious versions

1 flagged

35.8.5

Indicators of compromise (SHA-256)

749fb409dca041d1e546949cfb546398db8752d59153c18e675f691231f3f1c0

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

Campaign

IN-MAL-2026-015000

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-spa-plugin-query-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