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

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

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

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

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

Yes — devplatform-spa-plugin-auth is associated with the IN-MAL-2026-015015 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-auth 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-auth (version 35.4.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-auth across your stack and pipelines.

Malicious package

devplatform-spa-plugin-authnpm

devplatform-spa-plugin-auth is a confirmed malicious npm package (MAL-2026-12761) that steals credentials and exfiltrates sensitive data (malicious version 35.4.5). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12761

Immediate action

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

npm uninstall devplatform-spa-plugin-auth

What this malware does

The package's main entry loads helpers.js which auto-invokes a start() routine on require. That routine selects a platform-specific asset path, retrieves an opaque native binary over HTTPS from one of four Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT base64-chunk fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<rand> on Unix or %TEMP%/dotnet_diag_<rand>.exe on Windows, chmod 0755'd, and spawned detached via /bin/sh or cmd.exe. Hostnames and sensitive API references are assembled at runtime from string arrays (['oob-worker.cf100','-416.workers.de','v'].join(''); require('child_'+'process')), a '.analytics_state' marker file suppresses repeat runs, and stderr is silenced through a no-op writer. The package is advertised as an SPA auth-token plugin and has no legitimate reason to fetch and execute a native binary at load time. The delivered code is attacker-controlled and unverified, granting full-host code execution to whoever operates the Workers/DNS infrastructure on any machine that requires this module.

Malicious versions

1 flagged

35.4.5

Indicators of compromise (SHA-256)

697c6ca9c6aa1474e725b8f1c7d64c0b1809131ce1c8a856253db8d480791ff0

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-spa-plugin-auth (version 35.4.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-auth across your stack and pipelines.
If you installed it — respond
devplatform-spa-plugin-auth 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-spa-plugin-auth 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-auth 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-auth on npm has been identified as a malicious package (version 35.4.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015015

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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