Which versions of session-keeper are malicious?

The following npm versions of session-keeper are flagged malicious: 2.4.5, 2.5.5. Treat any of these as compromised.

How do I remediate session-keeper if I installed it?

Remove session-keeper 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 session-keeper — how do I know if it already compromised me?

If session-keeper 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.

Is session-keeper part of a known attack campaign?

Yes — session-keeper is associated with the RLMA-2025-06478, RLUA-2026-01559 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 session-keeper across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for session-keeper (2 malicious versions).

Malicious package

session-keepernpm

Advisory published Dec 23, 2025Updated Mar 19, 2026

session-keeper is a confirmed malicious npm package (MAL-2025-192861) that executes malicious code on install (malicious versions 2.4.5, 2.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in session-keeper (npm)

MAL-2025-192861

Immediate action

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

npm uninstall session-keeper

What this malware does

The package session-keeper was found to contain malicious code.

Malicious versions

2 flagged

2.4.52.5.5

Indicators of compromise (SHA-256)

9796e552c469adab7d20d2005b6e5d89b5c0625d6cd70beb932bb83250fab2de

6816e7c69a6752f4aeccba80eac83e7fd815e3388f21b4bfd007ccd6192dbc96

36c9a084822e58205fd29641345e07cde47d44621a5efd1a3aa55d93a5e21447

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for session-keeper (2 malicious versions).
If you installed it — respond
Remove session-keeper 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 session-keeper 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. session-keeper on npm has been identified as a malicious package (versions 2.4.5, 2.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06478RLUA-2026-01559

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks session-keeper-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

Explore

All malware advisories How O3 detects malware Vulnerability database