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

devplatform-spa-plugin-s3-module-loadernpm

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

Malicious code in devplatform-spa-plugin-s3-module-loader (npm)

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

What this malware does

On require of the package's main entry, index.js loads adapter.js, which selects a platform-specific payload URL, fetches opaque bytes from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) assembled from split string arrays, writes them to a hidden temp path (dot-file on Unix, dotnet_diag*.exe on Windows), chmods 0755 on Unix, and spawns the file detached via /bin/sh -c or cmd.exe /c start. A DNS-over-TXT fallback resolves c.<domain>/i.<domain> under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru and base64-reassembles a payload from numbered TXT records when HTTPS delivery is blocked. Destinations, delivery channels, and payloads are fully author-controlled, obfuscated via runtime string reassembly, and unrelated to the package's advertised S3-module-loader purpose. Cover-story identifiers include analytics_state and DISABLE_TELEMETRY.

Malicious versions

1 flagged
35.8.2

Indicators of compromise (SHA-256)

b1a4f4ab19296a9ece2741e6f813780cbdc84d5f7fe188024ad2deb51aa97b5a

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-014997

References

Credits

  • Amazon Inspector · finder

Detect & block this

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