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

ally-call-wait-timenpm

Malicious code in ally-call-wait-time (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3297
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ally-call-wait-time

What this malware does

The package ally-call-wait-time was found to contain malicious code.

The OpenSSF Package Analysis project identified 'ally-call-wait-time' @ 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)

c2d0a1ca7cc7414bc364d4bc0b6474660711cfdcf8e522499692e26afd555ff6
6f8c667e05a456ae18a25cc75ba3ca7c53ea00a376e795be78a5511036016111
20246193f2fbde13a2dccd6325c1d46a7fec7e8491b4df3ae6fefa85eff99bbf

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 ally-call-wait-time (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ally-call-wait-time across your stack and pipelines.

  2. If you installed it — respond

    Remove ally-call-wait-time 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 ally-call-wait-time 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 ally-call-wait-time 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. ally-call-wait-time 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.

Credits

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

Detect & block this

O3 blocks ally-call-wait-time-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.

ally-call-wait-time (npm) malicious package — MAL-2026-3297 | O3 Security