Which versions of credit-decision-metrics are malicious?

The following PyPI versions of credit-decision-metrics are flagged malicious: 9.1.0. Treat any of these as compromised.

How do I remediate credit-decision-metrics if I installed it?

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

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

Yes — credit-decision-metrics is associated with the 2026-02-zabitmajeed00, RLMA-2026-00228 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 credit-decision-metrics 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 credit-decision-metrics (version 9.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging credit-decision-metrics across your stack and pipelines.

Malicious package

credit-decision-metricsPyPI

Malicious code in credit-decision-metrics (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-653

Immediate action

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

pip uninstall credit-decision-metrics

What this malware does

Obfuscated code is used to hide exfiltration of basic data (hostname, etc.).

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2026-02-zabitmajeed00

Reasons (based on the campaign):

obfuscation
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
dependency-confusion

Malicious versions

1 flagged

9.1.0

Indicators of compromise (SHA-256)

4a0320017dad96c95d4741c311ead566b7d6bea0c7ffdceea82b435ce74a40de

d8e2c4b835c9deeaa4d98544c7ec6325d8e6e7fb2f3e08caf25ae7f618131204

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for credit-decision-metrics (version 9.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging credit-decision-metrics across your stack and pipelines.
If you installed it — respond
credit-decision-metrics 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 credit-decision-metrics 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 credit-decision-metrics 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. credit-decision-metrics on PyPI has been identified as a malicious package (version 9.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-zabitmajeed00RLMA-2026-00228

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst
ReversingLabs · finder

Detect & block this

O3 blocks credit-decision-metrics-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