NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

devplatform-spa-plugin-beavernpm

Advisory published Updated

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

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

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

What this malware does

On require(), the package's init.js selects a platform-specific URL from a set of Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) whose hostnames are assembled from split-string fragments to evade static grep, downloads an opaque binary payload with no hash or signature verification, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows using filenames disguised as system diagnostics, chmods 0o755, and detach-spawns it via /bin/sh -c or cmd /c start with unref() so the child outlives the require. A DNS-TXT covert channel over subdomains of sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru provides a fallback transport that reassembles base64 chunks from numbered TXT records, bypassing HTTP egress filtering. Execution is gated by cover-story opt-outs (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK) and a ~6h TTL marker at /tmp/.analytics_state or %TEMP%\analytics_state so the dropper fires once per fresh host to reduce detection surface. The fetched bytes have no relation to the advertised 'spa plugin' function, and the fetch destinations are neither the npm registry nor a publisher-matched vendor host.

Malicious versions

1 flagged
35.2.2

Indicators of compromise (SHA-256)

c4a35163a32dc9e4e60b1e9b09f33362ac19ea6e1486dfb4141a98a5263d1fa6

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for devplatform-spa-plugin-beaver (version 35.2.2).

  2. If you installed it — respond

    Remove devplatform-spa-plugin-beaver 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-beaver was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. devplatform-spa-plugin-beaver on npm has been identified as a malicious package (version 35.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015019

References

Credits

  • Amazon Inspector · finder

Detect & block this

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