What does the devplatform-vite-plugin-gle malware do?

On require(), _support.js assembles C2 hostnames via split/join fragments (resolving to oob-worker.cf100-416.workers.dev, cf103-070.workers.dev, cf101-adf.workers.dev) and downloads a platform-specific binary via https.get, with a DNS TXT fallback under dl.wel1.ru that reads a chunk count from c. and base64 chunks from N. . The fetched payload is written to %TEMP%/dotnet_diag_ .exe on Windows or /var/tmp/.cache_ on Unix, chmod 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref(). A /tmp/.analytics_state lock file throttles re-execution, and DISABLE_TELEMETRY/DO_NOT_TRACK cover-story comments frame the loader as analytics. No h

Which versions of devplatform-vite-plugin-gle are malicious?

The following npm versions of devplatform-vite-plugin-gle are flagged malicious: 35.3.9. Treat any of these as compromised.

How do I remediate devplatform-vite-plugin-gle if I installed it?

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

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

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

Malicious package

devplatform-vite-plugin-glenpm

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

Malicious code in devplatform-vite-plugin-gle (npm)

MAL-2026-13273

Immediate action

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

npm uninstall devplatform-vite-plugin-gle

What this malware does

On require(), support.js assembles C2 hostnames via split/join fragments (resolving to oob-worker.cf100-416.workers.dev, cf103-070.workers.dev, cf101-adf.workers.dev) and downloads a platform-specific binary via https.get, with a DNS TXT fallback under dl.wel1.ru that reads a chunk count from c.<domain> and base64 chunks from N.<domain>. The fetched payload is written to %TEMP%/dotnet_diag<hex>.exe on Windows or /var/tmp/.cache_<hex> on Unix, chmod 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref(). A /tmp/.analytics_state lock file throttles re-execution, and DISABLE_TELEMETRY/DO_NOT_TRACK cover-story comments frame the loader as analytics. No hash or signature check is performed on the downloaded binary. The package name mimics a legitimate Vite plugin.

Malicious versions

1 flagged

35.3.9

Indicators of compromise (SHA-256)

81ba08fb4c9c52336f51b45ebe9089ba0b441f3da79529ac1c56f146d71861b6

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

Campaign

IN-MAL-2026-015725

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-vite-plugin-gle-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