Which versions of newrelic-logging are malicious?

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

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

Remove newrelic-logging 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-logging — how do I know if it already compromised me?

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

Yes — newrelic-logging is associated with the GHSA-v57p-ww2g-c3f6, RLMA-2025-05079, RLUA-2026-01446 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-logging 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-logging (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-logging across your stack and pipelines.

Malicious package

newrelic-loggingnpm

newrelic-logging is a confirmed malicious npm package (MAL-2025-47194) 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-logging (npm)

MAL-2025-47194

Immediate action

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

npm uninstall newrelic-logging

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)

9474b4b491d2662f1018b623e7ee7428918e6c007d0faa6aad7fbcc3d067d78e

242edb81d7f6b6d52f6595a5942cd10483f5a4177e043bebfc10e756222aee81

10eb36ed9c9a4f7391377c11016b1855772229beabc491353e8c7633bdf897e7

c14cadd45e989b7c9432626c79be1cc2fd143f823dbcec6ac5153f975d91a7b4

c08ea2e92512c3090dab2e5fcb8a6015bf9cf135a650ff76221c648760037ca5

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-logging (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-logging across your stack and pipelines.
If you installed it — respond
Remove newrelic-logging 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-logging 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-logging 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-logging 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-v57p-ww2g-c3f6RLMA-2025-05079RLUA-2026-01446

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks newrelic-logging-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