Which versions of shop-minis are malicious?

The following npm versions of shop-minis are flagged malicious: 2.0.5. Treat any of these as compromised.

How do I remediate shop-minis if I installed it?

shop-minis is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed shop-minis — how do I know if it already compromised me?

If shop-minis 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.

Is shop-minis part of a known attack campaign?

Yes — shop-minis is associated with the IN-MAL-2026-004905, IN-MAL-2026-004906, GHSA-ghv6-vv2r-5f8v campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find shop-minis across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shop-minis (version 2.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shop-minis across your stack and pipelines.

Malicious package

shop-minisnpm

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

MAL-2026-4807

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall shop-minis

What this malware does

On npm install, the package's postinstall script (postinstall.js, run via scripts.postinstall = 'node postinstall.js') collects host identity — whoami, id, os.hostname(), os.platform(), current working directory, and the env vars CI, GITHUB_REPOSITORY, NODE_ENV — and sends them to the hardcoded attacker-controlled host svr57aylqme3zald4p0psi1hw827q1eq.oastify.com (a Burp Collaborator / OAST canary domain) via both https.get and DNS lookup. The package name shop-minis and self-described 'Security research canary — shopify' impersonate Shopify's Shop Minis platform, so any developer expecting that namespace would unwittingly leak host recon to the canary operator's collaborator instance. The package ships no real functionality matching its name; the only effect of installation is the exfiltration beacon.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.0.5

Indicators of compromise (SHA-256)

6e9e3e4e8e9e12bac20967fa551c549a93915b33007d7e54f8bfe0eed26a216e

7366059c37dc67acd2988ef814e67556fc226b983668520a41518ca39c14902e

15ec57895cae37229f449175b247b9d216d8b9e6f7d521341cfa6ffee413b07e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shop-minis (version 2.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shop-minis across your stack and pipelines.
If you installed it — respond
shop-minis is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If shop-minis 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.
How O3 protects you
O3 blocks shop-minis 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-minis on npm has been identified as a malicious package (version 2.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004905IN-MAL-2026-004906GHSA-ghv6-vv2r-5f8v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks shop-minis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring