Which versions of chess-sec-ssrf1 are malicious?

The following npm versions of chess-sec-ssrf1 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate chess-sec-ssrf1 if I installed it?

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

If chess-sec-ssrf1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find chess-sec-ssrf1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chess-sec-ssrf1 (version 1.0.1).

Malicious package

chess-sec-ssrf1npm

Advisory published Apr 6, 2026Updated Apr 7, 2026

chess-sec-ssrf1 is a confirmed malicious npm package (MAL-2026-2496) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chess-sec-ssrf1 (npm)

MAL-2026-2496

Immediate action

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

npm uninstall chess-sec-ssrf1

What this malware does

The package chess-sec-ssrf1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'chess-sec-ssrf1' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

74303ac236c7f5386e2fc96d7ac2a7bbf1d0054efcce03f04a10fe49216bd02e

25205345915fdf089bcbd90b35f9e852c02281bd7452805479d18c610063ac52

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chess-sec-ssrf1 (version 1.0.1).
If you installed it — respond
Remove chess-sec-ssrf1 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 chess-sec-ssrf1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. chess-sec-ssrf1 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks chess-sec-ssrf1-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