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

electron-sessionsnpm

Advisory published Updated

electron-sessions is a confirmed malicious npm package (MAL-2026-14266) that executes malicious code on install (malicious version 0.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in electron-sessions (npm)

MAL-2026-14266
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall electron-sessions

What this malware does

Package published as electron-sessions advertises itself as generic 'Session utilities' but ships a single 1.18MB heavily obfuscated dist/index.js (javascript-obfuscator with rotating string-array of length 4399, control-flow flattening, self-defending wrapper, dead-code injection) as both main and bin. The bundle contains plaintext substrings chrome, cookies, electron alongside an import of the @vercel/blob upload SDK (declared runtime dependency @vercel/blob: ^2.6.1), whose primary API uploads arbitrary bytes to a Vercel Blob store held by whoever controls the BLOB_READ_WRITE_TOKEN. Package naming targets Electron/Chromium session artifacts (cookies, Local Storage/leveldb, Login Data), the README exposes only a one-line new Sessions() cover-story API with no documented upload endpoint or caller-configurable destination, and the upload SDK has no legitimate purpose in a generic session-utilities library. Any process that runs npx electron-sessions or require('electron-sessions') executes the obfuscated bundle against its own host, and collected session data is shipped to an author-controlled Vercel Blob endpoint.

Malicious versions

1 flagged
0.1.5

Indicators of compromise (SHA-256)

cb868700350bb9700f3419a058a7802293ac0e39212ecd0c9f16eddb9e0af769

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for electron-sessions (version 0.1.5).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-018378

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks electron-sessions-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

electron-sessions (npm) malicious package — MAL-2026-14266 | O3 Security