Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@allybank/ally-sdknpm

Malicious code in @allybank/ally-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3289
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @allybank/ally-sdk

What this malware does

The package @allybank/ally-sdk 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 '@allybank/ally-sdk' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged
99.99.99100.0.0

Indicators of compromise (SHA-256)

67645939e4782ac1630fa76e169ab40440ba042733ae223bb3d4d77b1f635b86
3c3d4db9ae2585348864ec057b0a480e779a1c3a5105e48afe33b025a8beb871
d33aa2edae61b25d620c43d0a5a6223ff28bd128a7fdb5525d25b5c867d52568
36102348c36e1e062e95a9a3ace3f71e1a4529caabf224edab93d6eea31da2fd

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @allybank/ally-sdk (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @allybank/ally-sdk across your stack and pipelines.

  2. If you installed it — respond

    Remove @allybank/ally-sdk 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.

  3. Did it already run?

    If @allybank/ally-sdk 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.

  4. How O3 protects you

    O3 blocks @allybank/ally-sdk 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. @allybank/ally-sdk on npm has been identified as a malicious package (versions 99.99.99, 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2892-cpv4-xqr4

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @allybank/ally-sdk-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.

@allybank/ally-sdk (npm) malicious package — MAL-2026-3289 | O3 Security