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

express-session-jsnpm

Malicious code in express-session-js (npm) Remove it immediately and rotate any exposed credentials.

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

853f35820c1bfb3bd8be7548debc48dbf86de52a43e91d7b586a9b1ce86a54c7

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 (all published versions). 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 (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

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.

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