NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@b2b-portal/uchnpm

Advisory published Updated

@b2b-portal/uch is a confirmed malicious npm package (MAL-2026-2560) that executes malicious code on install (malicious version 4.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @b2b-portal/uch (npm)

MAL-2026-2560
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @b2b-portal/uch

What this malware does

The package @b2b-portal/uch 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.

The OpenSSF Package Analysis project identified '@b2b-portal/uch' @ 4.0.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
4.0.1

Indicators of compromise (SHA-256)

788cf7416f6a8a562c85b711f170c7c1aad0123d0bf4658d1eae3d1392996119
e559f0d2d934ad98bda8c11ca6613644ecf3f2584bee7e75c7edf59ecda35d37
89eb419e1f7beb102007973e2d226cb2cb5f534096cbc2be8dc538324f3f19db

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @b2b-portal/uch (version 4.0.1).

  2. If you installed it — respond

    Remove @b2b-portal/uch 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 @b2b-portal/uch 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. @b2b-portal/uch on npm has been identified as a malicious package (version 4.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-86jx-983h-h77x

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @b2b-portal/uch-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.

Explore

@b2b-portal/uch (npm) malicious package — MAL-2026-2560 | O3 Security