Which versions of nri-kube-events are malicious?

The following npm versions of nri-kube-events are flagged malicious: 8.9.12. Treat any of these as compromised.

How do I remediate nri-kube-events if I installed it?

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

If nri-kube-events 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 nri-kube-events part of a known attack campaign?

Yes — nri-kube-events is associated with the GHSA-4fwq-gvwc-9r38, RLMA-2025-05095, RLUA-2026-01467 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 nri-kube-events 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 nri-kube-events (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 nri-kube-events across your stack and pipelines.

Malicious package

nri-kube-eventsnpm

nri-kube-events is a confirmed malicious npm package (MAL-2025-47202) 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 nri-kube-events (npm)

MAL-2025-47202

Immediate action

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

npm uninstall nri-kube-events

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)

fd41beeed007957825a25616c5f002d1a7eb247ed5e96855252aa22c1de77479

ba7a7f0e1be61a46b8059cdc0b8d6dbf797988a4b02f1ee3ac02a613ed5c65a8

3f2674164464829b45e28773472a50ca5fc995271e59fa65468e83df62700e73

bc9e43bdbcde8d5e4ba75110e2402e4ac85b3bb15f48cbf925a38d9dd8bbe162

9de2723c036bf65684b0f002f5fdee21ebff2cd5613bffa0467fc0a13fd3eee0

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 nri-kube-events (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 nri-kube-events across your stack and pipelines.
If you installed it — respond
Remove nri-kube-events 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 nri-kube-events 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 nri-kube-events 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. nri-kube-events 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-4fwq-gvwc-9r38RLMA-2025-05095RLUA-2026-01467

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nri-kube-events-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