MalwarePublished 29 Jun 2026

@mcconnect/mcc-common-lib (npm) · Malicious Code

Affects @mcconnect/mcc-common-libSource GCVE Database

Malicious package : remove @mcconnect/mcc-common-lib and rotate any secrets on hosts that installed it.

Data as of 29 Jun 2026, 22:26 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6631

What to do

Remove @mcconnect/mcc-common-lib from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@mcconnect/mcc-common-lib	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package @mcconnect/mcc-common-lib contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, secure machine. Simply removing the package does not guarantee elimination of all malicious software introduced by it.

Impact

Full system compromise on any computer with the package installed or running. All stored secrets and keys on the affected system are at risk and should be considered compromised. The attacker may have persistent access beyond the presence of the package itself.

Defensive guidance

Remove the @mcconnect/mcc-common-lib package immediately. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Because full control of the system may have been given to an attacker, consider the system untrusted and perform a full forensic analysis and remediation beyond just removing the package.

Summary

The @mcconnect/mcc-common-lib npm package has been identified as malicious. Installation or execution of this package results in a full compromise of the affected system. Attackers may gain complete control, potentially exfiltrating secrets and keys stored on the machine. Due to the severity of the compromise, remediation involves not only removing the package but also rotating all credentials from a trusted environment, as the system may remain compromised even after removal.

References

github.com/advisories/GHSA-xpr4-wg5r-33c8 (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jun 2026, 22:26 UTC

Technical details

References

Community reviews