Which versions of err-notification are malicious?

The following npm versions of err-notification are flagged malicious: 1.0.0, 1.0.12, 1.0.14, 1.0.17, 1.1.12, 1.7.12. Treat any of these as compromised.

How do I remediate err-notification if I installed it?

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

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

Yes — err-notification is associated with the GHSA-ffxc-mjc8-gjwq, RLMA-2025-04997, RLUA-2026-01288 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 err-notification 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 err-notification (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging err-notification across your stack and pipelines.

Malicious package

err-notificationnpm

err-notification is a confirmed malicious npm package (MAL-2025-47177) that executes malicious code on install (malicious versions 1.0.0, 1.0.12, 1.0.14…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in err-notification (npm)

MAL-2025-47177

Immediate action

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

npm uninstall err-notification

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

6 flagged

1.0.01.0.121.0.141.0.171.1.121.7.12

Indicators of compromise (SHA-256)

f0eafe58cdd2171d0209fa3bbc4150f186232cd35115cfb537dde7dd1842e98e

bc24e4b28f83c50eca14f88d3e7a3362ec1db329694722fc7240a3610785b633

fad7f19efba7268519da65c367f55ea40190a26b4bf1f303845623f96e745bc5

9b4d85b5b933259eb35c7f0de7186fd02c1f6eca85eb332b1bb6d3d5dca995b1

62590bbca3021015945f21b5a0d3d863c3b1984270ecab321c17aa5d22678214

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

Campaign

GHSA-ffxc-mjc8-gjwqRLMA-2025-04997RLUA-2026-01288

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks err-notification-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