Which versions of u-chan-secrets are malicious?

The following npm versions of u-chan-secrets are flagged malicious: 5.2.1, 5.2.2. Treat any of these as compromised.

How do I remediate u-chan-secrets if I installed it?

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

If u-chan-secrets 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 u-chan-secrets part of a known attack campaign?

Yes — u-chan-secrets is associated with the GHSA-44c7-vxrp-h5fq 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 u-chan-secrets across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for u-chan-secrets (2 malicious versions).

Malicious package

u-chan-secretsnpm

Advisory published Nov 9, 2026Updated Nov 9, 2026

u-chan-secrets is a confirmed malicious npm package (MAL-2026-18777) that executes malicious code on install (malicious versions 5.2.1, 5.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in u-chan-secrets (npm)

MAL-2026-18777

Immediate action

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

npm uninstall u-chan-secrets

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

2 flagged

5.2.15.2.2

Indicators of compromise (SHA-256)

619be2223fd3495f02e8056622d411dab9e8dc8d08891620734f7a6a8b9fb568

a222972784ceb30908f1631db0948b9f63e64fea437b529d613c4c31d08df66e

Detection & response playbook

Malicious package

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

Campaign

GHSA-44c7-vxrp-h5fq

References

github.com

Detect & block this

O3 blocks u-chan-secrets-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