Which versions of crediteligibilityserv are malicious?

Every published version of crediteligibilityserv on npm is considered malicious. Remove the package entirely.

How do I remediate crediteligibilityserv if I installed it?

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

If crediteligibilityserv was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is crediteligibilityserv part of a known attack campaign?

Yes — crediteligibilityserv is associated with the GHSA-qghr-grpc-j36x 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 crediteligibilityserv across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for crediteligibilityserv (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crediteligibilityserv across your stack and pipelines.

Malicious package

crediteligibilityservnpm

crediteligibilityserv is a confirmed malicious npm package (MAL-2025-49333) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in crediteligibilityserv (npm)

MAL-2025-49333

Immediate action

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

npm uninstall crediteligibilityserv

What this malware does

The package crediteligibilityserv was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

1fa8366bf4fe89b58935e18ad0bb36ea1e7a8ca2dfc986c233ccf23660a7a255

87f33c286230c02ec71ab2049c00a4674e77535bf310fc7fc8a9065ec31ca3cd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for crediteligibilityserv (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crediteligibilityserv across your stack and pipelines.
If you installed it — respond
Remove crediteligibilityserv 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 crediteligibilityserv was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks crediteligibilityserv before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. crediteligibilityserv on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qghr-grpc-j36x

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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