Which versions of devplatform-nx-gle are malicious?

The following npm versions of devplatform-nx-gle are flagged malicious: 35.5.3. Treat any of these as compromised.

How do I remediate devplatform-nx-gle if I installed it?

Remove devplatform-nx-gle from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed devplatform-nx-gle — how do I know if it already compromised me?

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

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

Malicious package

devplatform-nx-glenpm

devplatform-nx-gle is a confirmed malicious npm package (MAL-2026-12723) that executes malicious code on install (malicious version 35.5.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-nx-gle (npm)

MAL-2026-12723

Immediate action

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

npm uninstall devplatform-nx-gle

What this malware does

On require() of devplatform-nx-gle, index.js side-loads a sibling module bridge.js inside a swallowing try/catch. bridge.js reconstructs hardcoded Cloudflare Workers hostnames from split string fragments joined at runtime (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), downloads a platform-specific native executable via https.get, writes it under /tmp or %TEMP% with decoy filenames such as dotnet_diag<rand>.exe or.cache<rand>, chmods it 0755, and spawns it detached via spawn("/bin/sh", ["-c",...]) or spawn("cmd",...). A DNS TXT-record channel over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru serves as a fallback delivery path. The advertised package purpose is a trivial no-op class described as a shared backend integration library; the dropper module is unrelated to that advertised API. Hostnames are constructed via string-join concatenation to defeat static string matching, and the try/catch around the _bridge require() silently suppresses failures.

Malicious versions

1 flagged

35.5.3

Indicators of compromise (SHA-256)

5c9ada1c90c8e8217f9020f02c530477f38a6fd89338f415c815413498036faf

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-nx-gle (version 35.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-nx-gle across your stack and pipelines.
If you installed it — respond
Remove devplatform-nx-gle from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If devplatform-nx-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-nx-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-nx-gle on npm has been identified as a malicious package (version 35.5.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015058

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-nx-gle-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database