Which versions of newrelic-pixie are malicious?

The following npm versions of newrelic-pixie are flagged malicious: 8.9.12. Treat any of these as compromised.

How do I remediate newrelic-pixie if I installed it?

Remove newrelic-pixie 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.

I already installed newrelic-pixie — how do I know if it already compromised me?

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

Yes — newrelic-pixie is associated with the GHSA-hmhv-5xgx-6qvf, RLMA-2025-05080, RLUA-2026-01447 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 newrelic-pixie 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 newrelic-pixie (version 8.9.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging newrelic-pixie across your stack and pipelines.

Malicious package

newrelic-pixienpm

newrelic-pixie is a confirmed malicious npm package (MAL-2025-47195) that executes malicious code on install (malicious version 8.9.12). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in newrelic-pixie (npm)

MAL-2025-47195

Immediate action

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

npm uninstall newrelic-pixie

What this malware does

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

8.9.12

Indicators of compromise (SHA-256)

16c7baf5c47666c1407211c9fb57ede68cd4a7eea34bd8e591af32fd24c11f5f

3ffe2351f68cb3b68ba25c7cd3a67f2259493c28042af9def3cb368e1b89b90f

3ae952f4a75b4f4df4ef1c2dbc295fc332fb60fc5ab2cb326bf9af178116ca5c

2bd51668a3f870cb70fc08dae022c449b28de2307178543d9f75273b379275c9

a14f1ca6edc94e78ddf0beffe45334a790c43980bd4d5803570df2becc64a264

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for newrelic-pixie (version 8.9.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging newrelic-pixie across your stack and pipelines.
If you installed it — respond
Remove newrelic-pixie 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 newrelic-pixie 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 newrelic-pixie 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. newrelic-pixie on npm has been identified as a malicious package (version 8.9.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hmhv-5xgx-6qvfRLMA-2025-05080RLUA-2026-01447

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks newrelic-pixie-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database