Which versions of cvbmxiowkwqla6 are malicious?

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

How do I remediate cvbmxiowkwqla6 if I installed it?

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

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

Yes — cvbmxiowkwqla6 is associated with the GHSA-mgr2-2cf3-5j8q, IN-MAL-2026-017524 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 cvbmxiowkwqla6 across my projects, lockfiles, and CI pipelines?

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

Malicious package

cvbmxiowkwqla6npm

Advisory published Aug 12, 2026Updated Aug 12, 2026

cvbmxiowkwqla6 is a confirmed malicious npm package (MAL-2026-13796) 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 cvbmxiowkwqla6 (npm)

MAL-2026-13796

Immediate action

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

npm uninstall cvbmxiowkwqla6

What this malware does

Package [email protected] contains only two files and no behaviors matching supply-chain attack patterns were identified. No lifecycle scripts, network calls, credential reads, or code-execution primitives are present in the analyzed contents. The package name is a random-looking string, which is consistent with placeholder, test, or throwaway publications.

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)

daa100d53a0c1be6b6a40e562f71082118d66584766ad756f84223beff044e39

0dbfcc7e82fc725383c9578e9d53c4e69bdf6af9ba8037d2bf9fa50dce51969e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for cvbmxiowkwqla6 (version 1.0.0).
If you installed it — respond
cvbmxiowkwqla6 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 cvbmxiowkwqla6 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. cvbmxiowkwqla6 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-mgr2-2cf3-5j8qIN-MAL-2026-017524

References

Credits

Amazon Inspector · finder

Detect & block this

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