@sflyinc-knapsack/shutterfly-reactnpm
@sflyinc-knapsack/shutterfly-react is a confirmed malicious npm package (MAL-2026-5393) that typosquats a legitimate package to trick installs (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @sflyinc-knapsack/shutterfly-react (npm)
What this malware does
On require/load, index.js collects host identifiers (os.hostname(), os.userInfo(), os.homedir()), DNS server configuration, package.json metadata, and __dirname, then HTTPS-POSTs them to nlc574f24tq03k423v3jr7hllcr3ft3i.oastify.com — a Burp Collaborator (OAST) subdomain. The package is published at version 999.0.0 under a scope mimicking an internal Shutterfly namespace, designed to win npm version resolution against the legitimate private package. Any installer who imports this package leaks host and internal-package metadata to an attacker-controlled endpoint. The package's own description self-identifies as a dependency-confusion proof-of-concept, but the live registry artifact still executes against any consumer that resolves it.
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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sflyinc-knapsack/shutterfly-react (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sflyinc-knapsack/shutterfly-react across your stack and pipelines.
If you installed it — respond
@sflyinc-knapsack/shutterfly-react is a typosquat — you almost certainly intended a legitimately-named package. Remove @sflyinc-knapsack/shutterfly-react, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @sflyinc-knapsack/shutterfly-react 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 @sflyinc-knapsack/shutterfly-react 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks @sflyinc-knapsack/shutterfly-react-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.