Which versions of unhandledrejection1 are malicious?

The following npm versions of unhandledrejection1 are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate unhandledrejection1 if I installed it?

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

If unhandledrejection1 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.

How do I find unhandledrejection1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for unhandledrejection1 (version 1.0.2).

Malicious package

unhandledrejection1npm

Advisory published Mar 22, 2026Updated Mar 23, 2026

unhandledrejection1 is a confirmed malicious npm package (MAL-2026-2082) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in unhandledrejection1 (npm)

MAL-2026-2082

Immediate action

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

npm uninstall unhandledrejection1

What this malware does

The package unhandledrejection1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'unhandledrejection1' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

77e22c910e188d936e242af099f6bf026ceace104d9c1da3e772ba7faad05595

3f2b4dcba608cf46c9d933fd9af75d42e1f10758f11890ea7afa67460e5c3ce1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for unhandledrejection1 (version 1.0.2).
If you installed it — respond
Remove unhandledrejection1 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 unhandledrejection1 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. unhandledrejection1 on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks unhandledrejection1-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