Which versions of accounts-base are malicious?

The following npm versions of accounts-base are flagged malicious: 23.5.6. Treat any of these as compromised.

How do I remediate accounts-base if I installed it?

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

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

Yes — accounts-base is associated with the GHSA-64q9-hhhw-wg7q 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 accounts-base 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 accounts-base (version 23.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging accounts-base across your stack and pipelines.

Malicious package

accounts-basenpm

Malicious code in accounts-base (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191480

Immediate action

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

npm uninstall accounts-base

What this malware does

The package accounts-base was found to contain malicious code.

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 'accounts-base' @ 23.5.6 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

23.5.6

Indicators of compromise (SHA-256)

91aded18014deeb9f278bcd61adcdf917bad7b7e50159b48c125f453f19681cf

07acaccf5cae78ad4bfd5f967e15c5ba68180c1350310492a9065ca97124bf26

cf76e57ba69c401756a0d9279f66fcd197667ce73a011c643099737d08dc306c

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

Campaign

GHSA-64q9-hhhw-wg7q

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks accounts-base-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