Which versions of @selfpentest/eslint-pentest-plugin are malicious?

The following npm versions of @selfpentest/eslint-pentest-plugin are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @selfpentest/eslint-pentest-plugin if I installed it?

@selfpentest/eslint-pentest-plugin 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 @selfpentest/eslint-pentest-plugin — how do I know if it already compromised me?

If @selfpentest/eslint-pentest-plugin 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 @selfpentest/eslint-pentest-plugin part of a known attack campaign?

Yes — @selfpentest/eslint-pentest-plugin is associated with the IN-MAL-2026-020686 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 @selfpentest/eslint-pentest-plugin 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 @selfpentest/eslint-pentest-plugin (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 @selfpentest/eslint-pentest-plugin across your stack and pipelines.

Malicious package

@selfpentest/eslint-pentest-pluginnpm

@selfpentest/eslint-pentest-plugin is a confirmed malicious npm package (MAL-2026-17293) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @selfpentest/eslint-pentest-plugin (npm)

MAL-2026-17293

Immediate action

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

npm uninstall @selfpentest/eslint-pentest-plugin

What this malware does

Package presents itself as an ESLint plugin but the exported plugin object is an empty shell. index.js unconditionally invokes a steal() routine at top level, so any require() of the package (including ESLint auto-loading the plugin) triggers the payload. The payload reads process.env.HOME and process.env.SECRET, reads the first 30 bytes of ~/.ssh/known_hosts via fs.readFileSync(path.join(os.homedir(), '/.ssh/known_hosts')), and issues an HTTP GET to http://localhost:1337/eslint with the collected values as URL query parameters. The package.json description and README state that the package 'pretends to be an eslint plugin but it steals secrets instead' and identify it as a supply-chain-attack demonstration. The exfiltration destination is loopback (127.0.0.1:1337), so bytes do not leave the host unless a local listener collects them, but the credential-read code path executes on every require of the package.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f338876601180482b20a42fbd799b9d4e1b059bf7d733b5db448f7fc6d3455ff

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 @selfpentest/eslint-pentest-plugin (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 @selfpentest/eslint-pentest-plugin across your stack and pipelines.
If you installed it — respond
@selfpentest/eslint-pentest-plugin 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 @selfpentest/eslint-pentest-plugin 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 @selfpentest/eslint-pentest-plugin 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. @selfpentest/eslint-pentest-plugin 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

IN-MAL-2026-020686

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @selfpentest/eslint-pentest-plugin-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

Explore

All malware advisories How O3 detects malware Vulnerability database