Which versions of stretchshop are malicious?

The following npm versions of stretchshop are flagged malicious: 0.7.5. Treat any of these as compromised.

How do I remediate stretchshop if I installed it?

Remove stretchshop 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 stretchshop — how do I know if it already compromised me?

If stretchshop 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 stretchshop part of a known attack campaign?

Yes — stretchshop is associated with the IN-MAL-2026-016653 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 stretchshop 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 stretchshop (version 0.7.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stretchshop across your stack and pipelines.

Malicious package

stretchshopnpm

stretchshop is a confirmed malicious npm package (MAL-2026-13460) that executes malicious code on install (malicious version 0.7.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stretchshop (npm)

MAL-2026-13460

Immediate action

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

npm uninstall stretchshop

What this malware does

package.json declares a postinstall hook that runs node demo/demo.js base, which shell-invokes git clone https://github.com/Wradgio/StretchShop-demo-data.git at mutable HEAD (no commit SHA, no tag, no integrity check) and then childProcess.forks db/demo_data.js from the freshly cloned tree. The cloned repository is owned by the personal GitHub account Wradgio, which does not match the package's publisher scope StretchShop. Whoever controls that GitHub account can push arbitrary JavaScript to the default branch and have it executed on every fresh top-level install of [email protected].

Malicious versions

1 flagged

0.7.5

Indicators of compromise (SHA-256)

479c1238e6380db5463eb3755b980f963d269b2b0874d464b9e1b3b65bd03f60

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stretchshop (version 0.7.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stretchshop across your stack and pipelines.
If you installed it — respond
Remove stretchshop 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 stretchshop 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 stretchshop 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. stretchshop on npm has been identified as a malicious package (version 0.7.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016653

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks stretchshop-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