GHSA-7338-2qv3-86fw: Malicious code in claims-acct-unlock (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (fe5161ec5e3bb6bc18d6975809d09281190c49b41a4f926dfa6a28cabf061e04) claims-acct-unlock@25.2.1 ships no source code; package.json declares a single dependency 'node-acct-utilssss21' resolved from a bare HTTPS tarball URL on an unrelated GitHub user's repository (github.com/GamerD11/pingtest) at the mutable branch ref refs/heads/main, with no commit pin and no integrity hash. On npm install, npm fetches whatever bytes are currently served at that URL and installs them as a dependency, running any lifecycle scripts bundled inside. The repository owner can replace the tarball contents at any time without any change to this package. The dependency name does not correspond to a known library and resembles a typo of an internal/utility package, consistent with a dependency-confusion / lure shape where the manifest itself is the entire attack surface.
Source: ghsa-malware (8babe157d3f6bb19849f2f205d0fba480425b9737ab89746796d63900bc90c8c) 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.
Source: ossf-package-analysis (49e97601227bdd6c1f90001323f6ec7ec7242416e3577d752dd5045453688a14) The OpenSSF Package Analysis project identified 'claims-acct-unlock' @ 25.2.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
- The package executes one or more commands associated with malicious behavior.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
npm/claims-acct-unlockfrom your environment.Remove the claims-acct-unlock package from any computer where it is installed or running.
- Operational
Immediately rotate all secrets and keys stored on any computer that has this package installed or running, using a different computer.
Event History
Frequently Asked Questions
Who is exposed to this issue?
Any computer where claims-acct-unlock@25.2.1 has been installed or run should be treated as fully compromised. Exposure occurs during npm installation because npm retrieves and installs the declared dependency from a mutable external tarball URL.
What does an attacker need to exploit this?
The owner of the referenced GitHub repository can replace the tarball contents served from its main branch at any time. No change to claims-acct-unlock is required, because the dependency is not pinned to a commit and has no integrity hash.
Are default npm installs affected?
Yes. The package manifest declares the external dependency, so a normal npm install fetches it automatically. Any lifecycle scripts included in the fetched dependency can run during installation.
What should be done if this package was installed or executed?
Treat the affected computer as compromised and rotate all secrets and keys stored on it. The available data does not provide a safe mitigation short of responding to the compromise.