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

@pimy-b2cweb/apiclient-commonnpm

Advisory published Updated

@pimy-b2cweb/apiclient-common is a confirmed malicious npm package (MAL-2026-15683) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @pimy-b2cweb/apiclient-common (npm)

MAL-2026-15683
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @pimy-b2cweb/apiclient-common

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

7e77f7c07d1a90586c5fe6afe9046fb232a9dc316f48c8693f1e38602b315397

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @pimy-b2cweb/apiclient-common (version 99.99.99).

  2. If you installed it — respond

    Remove @pimy-b2cweb/apiclient-common 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 @pimy-b2cweb/apiclient-common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @pimy-b2cweb/apiclient-common on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05898

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @pimy-b2cweb/apiclient-common-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

@pimy-b2cweb/apiclient-common (npm) malicious package — MAL-2026-15683 | O3 Security