MalwarePublished 3 Nov 2025Updated 18 Nov 2025

crediteligibilityserv (npm) · Malicious Code

Affects crediteligibilityservSource GCVE Database

Malicious package : remove crediteligibilityserv and rotate any secrets on hosts that installed it.

Data as of 13 Nov 2026, 19:51 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-49333

What to do

Remove crediteligibilityserv 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
npmcrediteligibilityserv	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 crediteligibilityserv contains malicious code that compromises any computer on which it is installed or running. Such a compromise implies full control by an outside entity, necessitating immediate removal of the package and rotation of all secrets and keys from a different, uncompromised system. Removal of the package alone may not eliminate all malicious software introduced by its installation.

Impact

Any system with the crediteligibilityserv package installed or running is considered fully compromised, potentially allowing attackers full control over the system. This compromises all stored secrets and keys, requiring immediate rotation from a different computer. The malicious code may have installed additional persistent malware beyond the package itself.

Defensive guidance

Remove the crediteligibilityserv package immediately. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Due to the likelihood of persistent malicious software, consider a full system rebuild or forensic analysis to ensure complete remediation.

Summary

The npm package crediteligibilityserv has been identified as containing malicious code. Installation or execution of this package results in a full compromise of the affected computer, granting an attacker complete control. Due to the severity of the compromise, all secrets and keys stored on the system should be rotated immediately from a secure, separate machine. Although the package should be removed, the presence of additional malicious software cannot be ruled out, meaning the system may remain compromised even after removal.

References

github.com/advisories/GHSA-qghr-grpc-j36x (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 19:51 UTC

Technical details

References

Community reviews