Which versions of newrelic-infra-operator are malicious?

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

How do I remediate newrelic-infra-operator if I installed it?

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

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

Yes — newrelic-infra-operator is associated with the GHSA-h4fp-gp2v-538p, RLMA-2025-05078, RLUA-2026-01445 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-infra-operator 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-infra-operator (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-infra-operator across your stack and pipelines.

Malicious package

newrelic-infra-operatornpm

newrelic-infra-operator is a confirmed malicious npm package (MAL-2025-47193) 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-infra-operator (npm)

MAL-2025-47193

Immediate action

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

npm uninstall newrelic-infra-operator

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)

0d13f7915d1227dc54cc2f1481a151b94b159d4ec2941d00db71133b636b5ed1

2ca5df945d9bef29d969c7d41151346f1bc3b19a73d359f90498ae44bbbca946

8e90cb10ca4e4e4d4b690110c2c4d8b6206f9929166ef0fbbde8e9c04112aa71

12281b3e184e1a4b5420578db7dda56f6d48a068ba00c27ddab67cce52949d9c

62b066c35a76f160dac9670f8e6d665432a3c9492e0741e06f9a89c131dc8168

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-infra-operator (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-infra-operator across your stack and pipelines.
If you installed it — respond
Remove newrelic-infra-operator 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-infra-operator 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-infra-operator 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-infra-operator 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-h4fp-gp2v-538pRLMA-2025-05078RLUA-2026-01445

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks newrelic-infra-operator-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