Which versions of express-sessions-id are malicious?

The following npm versions of express-sessions-id are flagged malicious: 3.6.9, 3.7.2, 3.7.3, 3.7.5. Treat any of these as compromised.

How do I remediate express-sessions-id if I installed it?

Remove express-sessions-id 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.

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

If express-sessions-id 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 express-sessions-id part of a known attack campaign?

Yes — express-sessions-id is associated with the GHSA-fj4q-29wj-89xc, RLMA-2026-01311 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 express-sessions-id 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 express-sessions-id (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-sessions-id across your stack and pipelines.

Malicious package

express-sessions-idnpm

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

MAL-2026-218

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall express-sessions-id

What this malware does

The package express-sessions-id 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

4 flagged

3.6.93.7.23.7.33.7.5

Indicators of compromise (SHA-256)

8255254d3d14b53c905d12727185c0f42a17d24b50bf67418f5f56f68950daa5

50976a5a79aa6e9a71eee66f3a74059d86a7620d670cf19ad43c9eb3619b0c2e

08126160af284e0cefc337920632fecbbc5df6425b56e05e841d9a333f0bdf44

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for express-sessions-id (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-sessions-id across your stack and pipelines.
If you installed it — respond
Remove express-sessions-id 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.
Did it already run?
If express-sessions-id 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 express-sessions-id 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-sessions-id on npm has been identified as a malicious package (versions 3.6.9, 3.7.2, 3.7.3, 3.7.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fj4q-29wj-89xcRLMA-2026-01311

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks express-sessions-id-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.

Malware detection Runtime egress monitoring