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

cold-debug-elevatornpm

cold-debug-elevator is a confirmed malicious npm package (MAL-2026-10409) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cold-debug-elevator (npm)

MAL-2026-10409
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cold-debug-elevator

What this malware does

The package presents itself as a debugging utility but its exported API is a browser credential stealer targeting installer-owned secrets. The extract(browserPath, outputPath) entry point spawns Chrome/Edge/Brave under a debugger, locates the OSCrypt App-Bound Encryption provider inside chrome.dll/msedge.dll via Zydis disassembly (searching for the OSCrypt.AppBoundProvider.Decrypt.ResultCode string), sets a hardware execute breakpoint, and reads the 32-byte AppBound key out of process registers via ReadProcessMemory. It then DPAPI-decrypts the Local State master key and issues SELECT... encrypted_value FROM cookies and SELECT origin_url, username_value, password_value FROM logins against every Chrome/Edge/Brave profile, AES-GCM-decrypting cookies, saved passwords, autofill and history. A second entry point extractGecko(outputPath) loads nss3.dll from installed Firefox, Thunderbird, Waterfox, SeaMonkey, Pale Moon, LibreWolf and Tor Browser and calls PK11SDR_Decrypt to recover saved passwords from logins.json, then copies cookies.sqlite, formhistory.sqlite and places.sqlite from each profile. Output files are delimited with a <Sage Private> branding string consistent with offensive tooling. binding.gyp references vcpkg paths outside the tarball (<(module_root_dir)\..\builder\src\Chromium-DebugElevator-main (1)\...), so node-gyp rebuild will fail on a normal install — the stealer is distributed as C++ source and runs only after a consumer builds it manually and invokes the API, but the shipped code has no purpose other than harvesting browser secrets from the machine that runs it.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

4 flagged
1.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

3defc6f8e0e63aff3ba2c8a1c152bde6d68bd0dda24ad9c14c1389236ee62ffd
5fe7b18c62acf544a82f1022bba7b58ed8995c5ea0387ac5f06783caffaf30e2
cae8ef53b42bfe7f208c404e2e973600fa174f41c5a2009814f5f0e892769195
6bfe2b635528545c3f811f608ded5e337a5c328bb077e9f9b729f40204bffaf4
8f6b43d7c40a2e55fe96949f2e4dfc8c7d081ba899015d505f8f7d678e17d939

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cold-debug-elevator (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cold-debug-elevator across your stack and pipelines.

  2. If you installed it — respond

    cold-debug-elevator is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If cold-debug-elevator 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 cold-debug-elevator 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. cold-debug-elevator on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009849IN-MAL-2026-009847IN-MAL-2026-009848GHSA-w47c-q2p5-gq33IN-MAL-2026-017995

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks cold-debug-elevator-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

cold-debug-elevator (npm) malicious package — MAL-2026-10409 | O3 Security