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

express-session-jsnpm

express-session-js is a confirmed malicious npm package (MAL-2026-2419) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-session-js (npm)

MAL-2026-2419
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall express-session-js

What this malware does

Package impersonates legitimate express-session package; initPlugin() downloads and executes attacker-controlled remote code on startup via new Function.constructor()

The package express-session-js was found to contain malicious code.

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

853f35820c1bfb3bd8be7548debc48dbf86de52a43e91d7b586a9b1ce86a54c7
3900af27585802d173eeb67aac372e9669193d07afe72a94019d1d6b19834d52

Detection & response playbook

Typosquat
  1. Find it

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

  2. If you installed it — respond

    express-session-js is a typosquat — you almost certainly intended a legitimately-named package. Remove express-session-js, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

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

Campaign

GHSA-2847-rm77-74wh

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks express-session-js-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

express-session-js (npm) malicious package — MAL-2026-2419 | O3 Security