Which versions of x-session-parser are malicious?

The following npm versions of x-session-parser are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate x-session-parser if I installed it?

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

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

Yes — x-session-parser is associated with the GHSA-6pr6-gwgp-hjj8, RLMA-2025-05201, RLUA-2025-05563, RLUA-2025-06002 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 x-session-parser 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 x-session-parser (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging x-session-parser across your stack and pipelines.

Malicious package

x-session-parsernpm

x-session-parser is a confirmed malicious npm package (MAL-2025-47023) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in x-session-parser (npm)

MAL-2025-47023

Immediate action

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

npm uninstall x-session-parser

What this malware does

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

1.0.0

Indicators of compromise (SHA-256)

656368dae017043edc5b926e1ca7ff9f6e3526b8de21a92a3ce573d70d89ba07

742f2bc56a2f19c1b29cc8dea0f125d20892ae02949ae277ac9635f9a932aac5

baa3b6a03a0e067ccb6d218556fd9881804db029b845ebc86378836e1a37a236

789a8f81a5f3922a457ba8e8f4cc8bff4b439aaa4fbb3b0a82334b9f6c800674

0788c2ab6d4751a8aead6806ff685be2f748f57912c5fb5be810314b5c038d43

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

Campaign

GHSA-6pr6-gwgp-hjj8RLMA-2025-05201RLUA-2025-05563RLUA-2025-06002

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks x-session-parser-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