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

@ascend-ops/web-clientnpm

Malicious code in @ascend-ops/web-client (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2575
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ascend-ops/web-client

What this malware does

The package @ascend-ops/web-client 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.

Malicious versions

1 flagged
99.9.0

Indicators of compromise (SHA-256)

e6aea2ffc9bdc8e7d4833898fc0de9c542bd8e22af96576d58d7031fd68a1a74
cdfb0d206a369a5dec9c804c41a0ed8b6cdc8855505a1fa991cfc568a85a58f3
57ec262f68b9b9bd081ce675c1eb28e56c6c630c03cf1ecb680e5b56035f0aaa

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 @ascend-ops/web-client (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ascend-ops/web-client across your stack and pipelines.

  2. If you installed it — respond

    Remove @ascend-ops/web-client 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 @ascend-ops/web-client 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 @ascend-ops/web-client 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. @ascend-ops/web-client on npm has been identified as a malicious package (version 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pqfr-rjg4-pjg3RLMA-2026-01849

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @ascend-ops/web-client-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.