Which versions of selenium-session-client are malicious?

The following npm versions of selenium-session-client are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate selenium-session-client if I installed it?

selenium-session-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed selenium-session-client — how do I know if it already compromised me?

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

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

Malicious package

selenium-session-clientnpm

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

MAL-2025-191422

Immediate action

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

npm uninstall selenium-session-client

What this malware does

The package selenium-session-client was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

5d530b6d9e91f5093b6a97dff0a72a315dec6bc139280b18c80bfc302cb9e72a

c213ecffb94ad5db9053c2dcf20681d6fe3a5baa0b8ed42d87e01c7ef930a704

20dcc48828b1cef715c653996bf6bb3e56e84e51421e9a1df589465843645429

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for selenium-session-client (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging selenium-session-client across your stack and pipelines.
If you installed it — respond
selenium-session-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If selenium-session-client 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 selenium-session-client 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. selenium-session-client on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06476

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks selenium-session-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring