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

@item-shop-data/clientnpm

@item-shop-data/client is a confirmed malicious npm package (MAL-2025-49104) that executes malicious code on install (malicious versions 0.0.1-security, 56.0.0, 56.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @item-shop-data/client (npm)

MAL-2025-49104
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @item-shop-data/client

What this malware does

The package @item-shop-data/client was found to contain malicious code.

Malicious versions

8 flagged
0.0.1-security56.0.056.0.356.0.1058.0.158.0.9058.90.9059.0.90

Indicators of compromise (SHA-256)

f3931756a8f0da8b385e1c2b974c51fef803ddf8c0c6cb84ed0dacf3b3e6c1bd

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

  2. If you installed it — respond

    Remove @item-shop-data/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 @item-shop-data/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 @item-shop-data/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. @item-shop-data/client on npm has been identified as a malicious package (versions 0.0.1-security, 56.0.0, 56.0.3, 56.0.10, 58.0.1, 58.0.90, 58.90.90, 59.0.90 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @item-shop-data/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

@item-shop-data/client (npm) malicious package — MAL-2025-49104 | O3 Security