Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

unhandledrejection1npm

Malicious code in unhandledrejection1 (npm) Remove it immediately and rotate any exposed credentials.

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
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for unhandledrejection1 (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unhandledrejection1 across your stack and pipelines.

  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.

  3. Did it already run?

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

  4. How O3 protects you

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

unhandledrejection1 (npm) malicious package — MAL-2026-2082 | O3 Security