Which versions of parse-session are malicious?

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

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

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

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

Yes — parse-session is associated with the GHSA-3w6m-fgww-62wh, RLMA-2025-06443 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 parse-session 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 parse-session (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 parse-session across your stack and pipelines.

Malicious package

parse-sessionnpm

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

MAL-2025-190630

Immediate action

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

npm uninstall parse-session

What this malware does

The package parse-session 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

2.4.1

Indicators of compromise (SHA-256)

5b04d6ff25ce91de5057fed89547b08687055f2ca7a217a2886eecb79c06f9e9

8e6800038c1b56247a0767faecf501d0c74de134197bb0edbae2d27b8a958547

e4e3634046e70731222973d03822e2a5672fb40776f4c3b95ec7feffa18e2e41

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 parse-session (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 parse-session across your stack and pipelines.
If you installed it — respond
Remove parse-session 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 parse-session 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 parse-session 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. parse-session 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

GHSA-3w6m-fgww-62whRLMA-2025-06443

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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