Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

devplatform-spa-plugin-remote-modulenpm

devplatform-spa-plugin-remote-module is a confirmed malicious npm package (MAL-2026-13547) that executes malicious code on install (malicious version 35.9.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-spa-plugin-remote-module (npm)

MAL-2026-13547
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall devplatform-spa-plugin-remote-module

What this malware does

On require of the package, index.js loads support.js which downloads a platform-specific binary from string-split-obfuscated hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev), with a DNS TXT fallback that reassembles a base64 payload from numbered subdomains under dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched binary is written to /var/tmp on Unix or %TEMP% on Windows under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmodded 0o755, and spawned detached via /bin/sh -c or cmd.exe /c start. Host strings and API names are reconstructed at runtime from array-join fragments (e.g., ["oob-worker.cf103-070.work","ers.d","ev"].join("")) to evade static analysis. A second module lib/telemetry.js ships the same dropper primitives with require("child_" + "process") and fs["chmod"+"Sync"] indirection, bundled as a ready-to-wire payload alongside the active dropper.

Malicious versions

1 flagged
35.9.6

Indicators of compromise (SHA-256)

995f8b1091ff43f5fae824ef6ac028895003b9a24960b78449cbc7b295aa34fd

Detection & response playbook

Malicious package

  1. 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-remote-module (version 35.9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-remote-module across your stack and pipelines.

  2. If you installed it — respond

    Remove devplatform-spa-plugin-remote-module 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.

  3. Did it already run?

    If devplatform-spa-plugin-remote-module 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.

  4. How O3 protects you

    O3 blocks devplatform-spa-plugin-remote-module 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-remote-module on npm has been identified as a malicious package (version 35.9.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017047

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-spa-plugin-remote-module-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
devplatform-spa-plugin-remote-module (npm) malicious package — MAL-2026-13547 | O3 Security