Which versions of shoplist-app are malicious?

The following npm versions of shoplist-app are flagged malicious: 99.99.99, 993.99.99. Treat any of these as compromised.

How do I remediate shoplist-app if I installed it?

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

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

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

Malicious package

shoplist-appnpm

shoplist-app is a confirmed malicious npm package (MAL-2026-17185) that steals credentials and exfiltrates sensitive data (malicious versions 99.99.99, 993.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shoplist-app (npm)

MAL-2026-17185

Immediate action

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

npm uninstall shoplist-app

What this malware does

[email protected] is a dependency-confusion / typosquat beacon. preinstall.js is wired into every lifecycle hook (preinstall, install, postinstall, prepare, prepublish) and issues an HTTPS GET to the hardcoded endpoint https://eo8f3m3ho26a0nm.m.pipedream.net/, transmitting the installer's machine hostname via os.hostname() (smuggled into a host HTTP header) together with package identity in the query string. index.js — the package main — independently fires a second HTTPS GET to the same Pipedream collector at require/import time, carrying os.platform() and a trigger=runtime marker. The package ships no functional code beyond these beacons; its version (99.99.99) and description ("test") are consistent with a name-squat probe designed to identify which internal build hosts resolve the name shoplist-app. The exfiltrated data (hostname, OS platform, package-name confirmation) gives the operator of the Pipedream endpoint a map of environments where a shoplist-app dependency reference successfully resolves to this public package — the standard reconnaissance stage of a dependency-confusion attack.

Malicious versions

2 flagged

99.99.99993.99.99

Indicators of compromise (SHA-256)

e93e834e421a980fa8418d93ad972f9f1c2ca56cbc7662b84e0627c19a8be248

fdceadb01f08162934382b121e813236b86adc0d4d74b7b2f062c78e529c34f6

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 shoplist-app (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shoplist-app across your stack and pipelines.
If you installed it — respond
shoplist-app 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 shoplist-app 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 shoplist-app 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. shoplist-app on npm has been identified as a malicious package (versions 99.99.99, 993.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020560IN-MAL-2026-020559

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks shoplist-app-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

Explore

All malware advisories How O3 detects malware Vulnerability database