Which versions of modern-events are malicious?

The following npm versions of modern-events are flagged malicious: 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.5.0, 1.5.1, 1.5.2. Treat any of these as compromised.

How do I remediate modern-events if I installed it?

modern-events is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed modern-events — how do I know if it already compromised me?

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

Yes — modern-events is associated with the GHSA-wwr2-883g-52c2, RLMA-2026-05162, RLUA-2026-05574 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 modern-events across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for modern-events (13 malicious versions).

Malicious package

modern-eventsnpm

Advisory published Apr 16, 2026Updated Jul 23, 2026

modern-events is a confirmed malicious npm package (MAL-2026-2914) that steals credentials and exfiltrates sensitive data (malicious versions 1.3.0, 1.3.1, 1.3.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in modern-events (npm)

MAL-2026-2914

Immediate action

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

npm uninstall modern-events

What this malware does

modern-events is a malicious npm package that when imported and using the function EventEmitter.emit(...) in file events.js exfiltrates local system information via telegram and slack and downloads a backdoor (Win64/FaxedCook) to C:/ProgramData/Policy/PublisherPolicy.tms.

The package modern-events 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

13 flagged

1.3.01.3.11.3.21.3.31.3.41.4.01.4.11.4.21.4.31.4.41.5.01.5.11.5.2

Indicators of compromise (SHA-256)

a97f17bfce91fabb0e7466807108d6b07b39eacee5166a4020065cae4b8b98f2

0a4d82014ce8355f8f1cde7a537ad359cd49981916ccc325e4a8a2128f7fff6b

73fb9ca795b6cd3b34f849ea29931b5144b327499383fadeef24d941bfbab905

179efe84c4797de3804293186b6861fd32066dd2331d409fb84a9ac0fc486024

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for modern-events (13 malicious versions).
If you installed it — respond
modern-events is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If modern-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. modern-events on npm has been identified as a malicious package (versions 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4.0, 1.4.1, 1.4.2, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wwr2-883g-52c2RLMA-2026-05162RLUA-2026-05574

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder
indece · finder

Detect & block this

O3 blocks modern-events-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database