Which versions of chmjdsidwlf5 are malicious?

The following npm versions of chmjdsidwlf5 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate chmjdsidwlf5 if I installed it?

chmjdsidwlf5 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed chmjdsidwlf5 — how do I know if it already compromised me?

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

Yes — chmjdsidwlf5 is associated with the GHSA-cgrq-g6cw-53vg, IN-MAL-2026-017525 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 chmjdsidwlf5 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chmjdsidwlf5 (version 1.0.0).

Malicious package

chmjdsidwlf5npm

Advisory published Aug 12, 2026Updated Aug 12, 2026

chmjdsidwlf5 is a confirmed malicious npm package (MAL-2026-13792) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chmjdsidwlf5 (npm)

MAL-2026-13792

Immediate action

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

npm uninstall chmjdsidwlf5

What this malware does

Package [email protected] contains 2 files with no a static rule matches and no traced behavior indicating exfiltration, install-time remote code execution, silent relay, credential distribution, backdoor, or self-propagation. The random-looking package name is unusual, but name shape alone is not a threat and the code performs no installer-facing harmful action.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

17d13e64fe5ff4370b5d93e448199b4e3bc75347808f36aa4a5f355872b7440e

e5c33467a3378e72f39a5093bded42a1aba6c08cca38cd631ea1ecc233e0377a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for chmjdsidwlf5 (version 1.0.0).
If you installed it — respond
chmjdsidwlf5 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If chmjdsidwlf5 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. chmjdsidwlf5 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cgrq-g6cw-53vgIN-MAL-2026-017525

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chmjdsidwlf5-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database