Which versions of @apps-legacy-reports/events are malicious?

The following npm versions of @apps-legacy-reports/events are flagged malicious: 9.10.8. Treat any of these as compromised.

How do I remediate @apps-legacy-reports/events if I installed it?

Remove @apps-legacy-reports/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 @apps-legacy-reports/events — how do I know if it already compromised me?

If @apps-legacy-reports/events was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @apps-legacy-reports/events part of a known attack campaign?

Yes — @apps-legacy-reports/events is associated with the RLMA-2026-04668, RLUA-2026-05810 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 @apps-legacy-reports/events across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @apps-legacy-reports/events (version 9.10.8).

Malicious package

@apps-legacy-reports/eventsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@apps-legacy-reports/events is a confirmed malicious npm package (MAL-2026-7038) that executes malicious code on install (malicious version 9.10.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @apps-legacy-reports/events (npm)

MAL-2026-7038

Immediate action

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

npm uninstall @apps-legacy-reports/events

Malicious versions

1 flagged

9.10.8

Indicators of compromise (SHA-256)

2b0d72435d8ec7d98c8c74b6a268207351eda98fdf611ef77d49099b8d36c6b3

fb0cecedec5869d5b482884feccf7f3b517e923d08e515066651909a1f210f95

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @apps-legacy-reports/events (version 9.10.8).
If you installed it — respond
Remove @apps-legacy-reports/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 @apps-legacy-reports/events was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @apps-legacy-reports/events on npm has been identified as a malicious package (version 9.10.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04668RLUA-2026-05810

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @apps-legacy-reports/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