Which versions of rum-events-format are malicious?

The following npm versions of rum-events-format are flagged malicious: 1.0.0, 10.1.0. Treat any of these as compromised.

How do I remediate rum-events-format if I installed it?

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

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

Yes — rum-events-format is associated with the GHSA-wxhj-h5c7-c92j, RLMA-2025-06465, RLUA-2026-01543 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 rum-events-format 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 rum-events-format (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rum-events-format across your stack and pipelines.

Malicious package

rum-events-formatnpm

Malicious code in rum-events-format (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192417

Immediate action

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

npm uninstall rum-events-format

What this malware does

The package rum-events-format was found to contain malicious code.

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

2 flagged

1.0.010.1.0

Indicators of compromise (SHA-256)

6c16e9cdb5fb7b68c70e047d538e96a46ea7125d0956e094d05c7c6242057538

1f6a17ba09614cd69d096859385577957b2737a3dce290dda9712c51fd7179c5

e4c37d8dd73fb6990e788e26d0488899326e23852306eb516063e4e1021bb465

33d917b6a8699d9f759f07b1f9df8bf685d6dcf76ba5cd8cb982489aa1ed6299

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 rum-events-format (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rum-events-format across your stack and pipelines.
If you installed it — respond
Remove rum-events-format 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 rum-events-format 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 rum-events-format 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. rum-events-format on npm has been identified as a malicious package (versions 1.0.0, 10.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wxhj-h5c7-c92jRLMA-2025-06465RLUA-2026-01543

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks rum-events-format-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