Which versions of session-validate are malicious?

The following npm versions of session-validate are flagged malicious: 2.2.4, 2.2.6. Treat any of these as compromised.

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

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

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

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

Malicious package

session-validatenpm

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

MAL-2025-191586

Immediate action

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

npm uninstall session-validate

What this malware does

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

Malicious versions

2 flagged

2.2.42.2.6

Indicators of compromise (SHA-256)

bff5ac17a2607f91faa5d24a60de6aa603dfee3517d8e626394260e6a4ab5f9b

91001b31023cb6f1a30d084b1c484e703936c4378ac7b76fc85dd023771cd8d2

2baff92083ec620c268cc5f62644cfed43b773f115adb70f916c87ac5f7ff0a1

9ce1b0f141873cb25e0a971b603b10b1b840dc92824a6a40884d7600f7a82a30

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

Campaign

RLMA-2025-05943RLUA-2025-06480RLUA-2026-01561

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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