Malicious Package in bitcroe-lib

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets. Recommendation 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.

Published by the source

4 Sep 2020, 16:45 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4m3p-x2hp-2pgx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4m3p-x2hp-2pgx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-4m3p-x2hp-2pgx

Advisory: Malicious Package in bitcroe-lib
IDs: GHSA-4m3p-x2hp-2pgx
Record: https://patchnext.com/advisories/ghsa-4m3p-x2hp-2pgx (revision 2, source checked 26 Oct 2026, 12:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm bitcroe-lib: affected every version

## Suggested inspection (read-only)
- `npm ls bitcroe-lib --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on bitcroe-lib.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4m3p-x2hp-2pgx (OSV record GHSA-4m3p-x2hp-2pgx lists affected ranges: npm bitcroe-lib >=0.0.0)
- Verified: https://github.com/advisories/GHSA-4m3p-x2hp-2pgx (GitHub-reviewed advisory GHSA-4m3p-x2hp-2pgx lists affected ranges: npm bitcroe-lib >=0.0.0)

Commands are suggestions: review each one before running it.