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

@biz44/id10-clientnpm

@biz44/id10-client is a confirmed malicious npm package (MAL-2026-16165) that executes malicious code on install (malicious version 1.1.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @biz44/id10-client (npm)

MAL-2026-16165
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @biz44/id10-client

What this malware does

This package is part of a malicious npm campaign published by the biz44 account. Importing the package automatically launches a detached JavaScript loader that retrieves and executes additional code from npoint.io. The retrieved payload communicates with an attacker-controlled server and implements clipboard collection, keyboard and mouse event collection, filesystem scanning, and theft of Chrome extension storage.

Malicious versions

1 flagged
1.1.11

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

  2. If you installed it — respond

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

Credits

  • ESTsecurity · finder

Detect & block this

O3 blocks @biz44/id10-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.

Explore

@biz44/id10-client (npm) malicious package — MAL-2026-16165 | O3 Security