Which versions of consumerweb-creditcollection are malicious?

The following npm versions of consumerweb-creditcollection are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate consumerweb-creditcollection if I installed it?

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

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

Yes — consumerweb-creditcollection is associated with the IN-MAL-2026-016671, GHSA-5h26-cm3q-vvcf 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 consumerweb-creditcollection 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 consumerweb-creditcollection (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging consumerweb-creditcollection across your stack and pipelines.

Malicious package

consumerweb-creditcollectionnpm

consumerweb-creditcollection is a confirmed malicious npm package (MAL-2026-13441) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in consumerweb-creditcollection (npm)

MAL-2026-13441

Immediate action

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

npm uninstall consumerweb-creditcollection

What this malware does

[email protected] is a hollow package whose main index.js exports an empty object. Its sole runtime effect is pulling in a dependency ltidisafe pinned to an arbitrary tarball URL on a third-party Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.5.3.tgz) rather than an npm registry entry. Installing this package causes npm to download and install code from that off-registry URL, which is outside npm registry scanning. The depenconf path segment, the internal-sounding package name, and the high version number 99.9.1 are consistent with a dependency-confusion / namespace-squat delivery vector where the lure package's only purpose is to force resolution of attacker-hosted code into the installer's dependency tree.

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

99.9.1

Indicators of compromise (SHA-256)

d1d673b014d7769d23ec9252c38424a3d1e2b400756cafa605f65383d93da348

7b8342fbe9749c59a330df358afb2418fcc69c217355d498c4c50d84fb8b7260

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 consumerweb-creditcollection (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging consumerweb-creditcollection across your stack and pipelines.
If you installed it — respond
Remove consumerweb-creditcollection 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 consumerweb-creditcollection 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 consumerweb-creditcollection 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. consumerweb-creditcollection on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016671GHSA-5h26-cm3q-vvcf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks consumerweb-creditcollection-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