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

shop-api-sdknpm

Malicious code in shop-api-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192378
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall shop-api-sdk

What this malware does

The package shop-api-sdk was found to contain malicious code.

The OpenSSF Package Analysis project identified 'shop-api-sdk' @ 30.1.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
30.0.030.1.1

Indicators of compromise (SHA-256)

55244eb11c1f0ccb519ddea9ad901abde196c9cd9387c8a4eb3267df5fcff846
a0306448f7e93f12777f1ee6bfa83d502c06b0a61ae631c612fabd3f8a5d6021
9df88087925552afbc95cc8c1ff4512887367255636165d692095bf3bbec52c5

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

  2. If you installed it — respond

    Remove shop-api-sdk 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 shop-api-sdk 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 shop-api-sdk 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. shop-api-sdk on npm has been identified as a malicious package (versions 30.0.0, 30.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks shop-api-sdk-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.

shop-api-sdk (npm) malicious package — MAL-2025-192378 | O3 Security