playwright-confignpm
Advisory published Updated
playwright-config is a confirmed malicious npm package (MAL-2026-20111) that executes malicious code on install (malicious version 20.20.20). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in playwright-config (npm)
What this malware does
Malicious package. A preinstall (and preupdate) script runs node index.js, which reads /etc/passwd (and attempts the Windows SAM hive and C:\Users), lists the current working directory, runs id/whoami, collects the user name, home directory, UID/GID and OS release, and posts it all to a hardcoded Discord webhook (1471187072869073017). The code labels its messages "Dependency Confusion Executed" and "Bug Bounty Execution", but it runs without consent on any machine that installs it. index.js (sha256 fb8451975ead2a956d3d8092eb2868d1ba9135fb6ef30e75941b1454958f75ae) is shared by canvas_webgl_minimal and playwright-config; the same webhook is used by google-caja-bower (MAL-2026-10186). Published 2026-02-23 and unpublished from npm on 2026-02-24.
Malicious versions
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for playwright-config (version 20.20.20).
If you installed it — respond
Remove playwright-config 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 playwright-config 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
References
Credits
- wormsign · finder
Detect & block this
O3 blocks playwright-config-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.