claims-acct-unlocknpm
Advisory published Updated
claims-acct-unlock is a confirmed malicious npm package (MAL-2026-18404) that executes malicious code on install (malicious version 25.2.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in claims-acct-unlock (npm)
What this malware does
[email protected] 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/ping_test) 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.
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for claims-acct-unlock (version 25.2.1).
If you installed it — respond
Remove claims-acct-unlock 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 claims-acct-unlock was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks claims-acct-unlock-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.