Which versions of @item-shop-data/client are malicious?

The following npm versions of @item-shop-data/client are flagged malicious: 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. Treat any of these as compromised.

How do I remediate @item-shop-data/client if I installed it?

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.

I already installed @item-shop-data/client — how do I know if it already compromised me?

If @item-shop-data/client 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.

How do I find @item-shop-data/client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @item-shop-data/client (8 malicious versions).

Malicious package

@item-shop-data/clientnpm

Advisory published Oct 30, 2025Updated Jun 10, 2026

@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

Find it
Search your lockfiles and build artifacts for @item-shop-data/client (8 malicious versions).
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.
Did it already run?
If @item-shop-data/client 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. @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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database