Which versions of @testrelic/playwright-analytics are malicious?

The following npm versions of @testrelic/playwright-analytics are flagged malicious: 2.13.0. Treat any of these as compromised.

How do I remediate @testrelic/playwright-analytics if I installed it?

@testrelic/playwright-analytics 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 @testrelic/playwright-analytics — how do I know if it already compromised me?

If @testrelic/playwright-analytics 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 @testrelic/playwright-analytics part of a known attack campaign?

Yes — @testrelic/playwright-analytics is associated with the IN-MAL-2026-019149 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 @testrelic/playwright-analytics 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 @testrelic/playwright-analytics (version 2.13.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @testrelic/playwright-analytics across your stack and pipelines.

Malicious package

@testrelic/playwright-analyticsnpm

@testrelic/playwright-analytics is a confirmed malicious npm package (MAL-2026-15565) that steals credentials and exfiltrates sensitive data (malicious version 2.13.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @testrelic/playwright-analytics (npm)

MAL-2026-15565

Immediate action

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

npm uninstall @testrelic/playwright-analytics

What this malware does

scripts/postinstall.cjs is registered as the package's postinstall lifecycle script and runs automatically on npm install. After a block of legitimate-looking config-scaffolding code, the file contains roughly 7 KB of whitespace padding followed by an obfuscated payload that reconstructs a large string via a custom Fisher–Yates shuffle, resolves the String constructor property (Function) to avoid any literal Function/eval token, and invokes Function('', decodedBody)(decodedArg). Immediately before the invocation the script assigns require, module, __dirname, and __filename onto the global object so the decoded body can load arbitrary Node built-ins. The whitespace gap conceals the payload from casual review of the file, and the indirection through String[constructor] avoids the literal tokens static reviewers grep for. The bundled dist/index.cjs, dist/reporter-entry.cjs, and dist/cli.cjs additionally contain require('child_process') alongside outbound HTTP POST call sites and ping invocations. The package's declared identity (a Playwright analytics reporter under an unfamiliar @testrelic scope) is inconsistent with shipping an obfuscated postinstall dynamic-code loader.

Malicious versions

1 flagged

2.13.0

Indicators of compromise (SHA-256)

c305bbe247587c98b06f039cdcf78066dbcd4fdacf5a5de0411023c2a4fcc97a

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

Campaign

IN-MAL-2026-019149

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @testrelic/playwright-analytics-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