Which versions of cit-playwright-tests are malicious?

The following npm versions of cit-playwright-tests are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate cit-playwright-tests if I installed it?

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

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

Yes — cit-playwright-tests is associated with the GHSA-64p5-3wp7-v4c9 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 cit-playwright-tests 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 cit-playwright-tests (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cit-playwright-tests across your stack and pipelines.

Malicious package

cit-playwright-testsnpm

Malicious code in cit-playwright-tests (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2080

Immediate action

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

npm uninstall cit-playwright-tests

What this malware does

The package cit-playwright-tests was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

f930d19684fcf0be0ffdfe252957aa458e3b5885f383641dc040880dd7a991b6

b7b3ed19c372c719b1d1b35ada72bf080aa8bc45406114b8361a94360bf2eb48

884531d509eae2bce24c8b5e2c97d9192a664fa9f7a47f2059e5e7695e2d2b89

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 cit-playwright-tests (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cit-playwright-tests across your stack and pipelines.
If you installed it — respond
cit-playwright-tests 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 cit-playwright-tests 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 cit-playwright-tests 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. cit-playwright-tests 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.

Campaign

GHSA-64p5-3wp7-v4c9

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cit-playwright-tests-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