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

devplatform-spa-plugin-sentrynpm

devplatform-spa-plugin-sentry is a confirmed malicious npm package (MAL-2026-12780) that typosquats a legitimate package to trick installs (malicious version 35.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

On require, index.js loads helpers.js which fetches an OS/arch-specific native binary from obfuscated Cloudflare Workers subdomains (oob-worker.cf9-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT covert-channel fallback under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru that reassembles a base64 payload from numbered subdomains. The fetched bytes are written to /tmp as a hidden dotfile (or to the Windows temp directory as dotnet_diag<rand>.exe), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled from split string fragments joined at runtime to evade static inspection, and dropped filenames (analytics_state, dotnet_diag_,.cache_) impersonate unrelated system tooling. The package presents itself as a Sentry SPA plugin but has no legitimate need to download and execute a native binary from anonymous Cloudflare Workers infrastructure.

Malicious versions

1 flagged
35.1.1

Indicators of compromise (SHA-256)

e2827eaf1f2c14fe16fc0fcab1ad65266f275fb22a9a81237d93f8e93e84894f

Detection & response playbook

Typosquat

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

  2. If you installed it — respond

    devplatform-spa-plugin-sentry is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-spa-plugin-sentry, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

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

Campaign

IN-MAL-2026-014990

References

Credits

  • Amazon Inspector · finder

Detect & block this

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