Which versions of clickpy are malicious?

The following npm versions of clickpy are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate clickpy if I installed it?

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

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

Yes — clickpy is associated with the IN-MAL-2026-004386, IN-MAL-2026-004253, IN-MAL-2026-004389 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 clickpy 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 clickpy (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging clickpy across your stack and pipelines.

Malicious package

clickpynpm

Malicious code in clickpy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4270

Immediate action

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

npm uninstall clickpy

What this malware does

On require('clickpy'), index.js collects host metadata via os.hostname(), os.userInfo(), os.platform(), os.arch(), process.cwd(), process.pid, and the current time, then issues an HTTPS GET to the hardcoded out-of-band host fxpkkxatijbbyxuhdclqssj033zarohm1.oast.fun with these values as query-string parameters (index.js:4 and index.js:25-29). oast.fun is the interactsh/OAST collaborator service used to receive callbacks from victim hosts; there is no legitimate purpose for a published library to beacon installer identifiers to such a host on import. Package metadata is empty (no description, no author), consistent with a throwaway recon/PoC exfiltration package.

The OpenSSF Package Analysis project identified 'clickpy' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

4eabe2c137602d61ffca6cc787c74601220c1e92f9b77300775a94327b784600

dd3b0787797fa520a5583fd5f14b83ec1b4606c0c45051e30ef312869c148f01

41e40fb2fc334582046d0e03983f4099343239a00886333fe924d5b6f093f4fe

6168bc8825a452e85328ec4a78bc82916c4a1dd1030593778093c576c6cc8d98

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

Campaign

IN-MAL-2026-004386IN-MAL-2026-004253IN-MAL-2026-004389

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks clickpy-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