Which versions of electron-sessions are malicious?

The following npm versions of electron-sessions are flagged malicious: 0.1.5. Treat any of these as compromised.

How do I remediate electron-sessions if I installed it?

electron-sessions 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.

I already installed electron-sessions — how do I know if it already compromised me?

If electron-sessions 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.

Is electron-sessions part of a known attack campaign?

Yes — electron-sessions is associated with the IN-MAL-2026-018378 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find electron-sessions across my projects, lockfiles, and CI pipelines?

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

Malicious package

electron-sessionsnpm

electron-sessions is a confirmed malicious npm package (MAL-2026-14266) that steals credentials and exfiltrates sensitive data (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

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for electron-sessions (version 0.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging electron-sessions across your stack and pipelines.
If you installed it — respond
electron-sessions 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.
Did it already run?
If electron-sessions 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.
How O3 protects you
O3 blocks electron-sessions 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. 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

npmjs.com

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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database