Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@testrelic/appium-analyticsnpm

Advisory published Updated

@testrelic/appium-analytics is a confirmed malicious npm package (MAL-2026-15647) that executes malicious code on install (malicious version 1.1.1-next.88). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-15647
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @testrelic/appium-analytics

What this malware does

The package registers scripts/postinstall.cjs as an npm postinstall hook. Alongside a benign-looking config-writer, the script contains an obfuscation layer that uses a custom Fisher-Yates-style permutation (Dbv) to reconstruct the string 'constructor' from a scrambled seed, resolves it against a function object to obtain the Function constructor, decodes a scrambled payload body, and invokes Function('', <decoded>)() at install time. Before invocation the wrapper stashes require, module, __dirname and __filename onto global under obfuscated keys so the decoded body can reach Node's module and filesystem APIs from within the Function() scope. The dist/ bundle additionally imports child_process and issues POST/GET calls from multiple files (dist/cli.cjs, dist/index.cjs, dist/service.cjs). No legitimate analytics/config bootstrap requires decoding an opaque scrambled string and executing it through Function.constructor, and the deliberate scope-escape scaffolding is characteristic of install-time droppers. The payload runs automatically on npm install on every installer machine.

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.

Malicious versions

1 flagged
1.1.1-next.88

Indicators of compromise (SHA-256)

646f0dd17193e933882467e3c5e420f4d4e43611de485b52a33385b5aac13fda
0b67d6f23451a756c154b86142f91615f5c08c415166c1f66216c8c83d74cbeb

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @testrelic/appium-analytics (version 1.1.1-next.88).

  2. If you installed it — respond

    Remove @testrelic/appium-analytics 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.

  3. Did it already run?

    If @testrelic/appium-analytics 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

No. @testrelic/appium-analytics on npm has been identified as a malicious package (version 1.1.1-next.88 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6cpr-jwvc-jhg7IN-MAL-2026-019389

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@testrelic/appium-analytics (npm) malicious package — MAL-2026-15647 | O3 Security