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

devplatform-spa-plugin-cobrowsingnpm

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

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

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

What this malware does

On require() of the package, index.js loads runtime.js which selects a platform-specific endpoint, downloads an opaque binary over HTTPS from obfuscated Cloudflare Workers hosts (hostnames assembled at runtime via array-join, e.g. 'oob-worker.cf<NNN>-<hex>.workers.dev'), with a DNS TXT-record fallback channel under 'c.<domain>' / 'N.<domain>' that returns base64-encoded chunks decoded into the payload. The downloaded bytes are written to /tmp/.cache<rand> (chmod 0755) on Unix or %TEMP%/dotnet_diag_<rand>.exe on Windows, and spawned detached via cp.spawn('/bin/sh',['-c',fp+' &'],{detached:true}).unref() or a cmd equivalent. Destinations are unrelated to the package's stated cobrowsing purpose, hostnames are obfuscated to defeat static analysis, and the payload is executed with no integrity check.

Malicious versions

1 flagged
35.4.4

Indicators of compromise (SHA-256)

96860be3701b6237d300a1c6e6bc23ff724f14557543451e221b255aff08a29e

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015010

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

devplatform-spa-plugin-cobrowsing (npm) malicious package — MAL-2026-12763 | O3 Security