Which versions of session-parse are malicious?

The following npm versions of session-parse are flagged malicious: 2.4.1. Treat any of these as compromised.

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

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

If session-parse 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 session-parse part of a known attack campaign?

Yes — session-parse is associated with the RLMA-2025-06479, RLUA-2026-01560 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-parse 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 session-parse (version 2.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging session-parse across your stack and pipelines.

Malicious package

session-parsenpm

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

MAL-2025-192862

Immediate action

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

npm uninstall session-parse

What this malware does

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

Malicious versions

1 flagged

2.4.1

Indicators of compromise (SHA-256)

818df27e879924b17c440eda15b039cefd5674dabee6f9f3e9aced304c89f630

40a7de8c7f167cc93ce3dc5b7530196018006f0eb6deae6d509659922417c495

a46ee2fb3c94e6131c462d9b44614c22915b7ceb6e125c162f4cd6bac7a6aafd

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 session-parse (version 2.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging session-parse across your stack and pipelines.
If you installed it — respond
Remove session-parse 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-parse 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 session-parse 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. session-parse on npm has been identified as a malicious package (version 2.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06479RLUA-2026-01560

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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