@demica/sharednpm
@demica/shared is a confirmed malicious npm package (MAL-2026-5351) that steals credentials and exfiltrates sensitive data (malicious versions 99.99.99, 99.99.100). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @demica/shared (npm)
What this malware does
Note: This report is updated by a verification record
Dep-confusion squat of internal @demica/shared at sentinel high version 99.99.100 + auto-exec postinstall (canary.js) beaconing to RAW IP 157.230.17.236:80/dc. Sentinel-high-version + auto-exec beacon = MALICIOUS per operator policy (c913); "authorized canary" framing does NOT downgrade, raw-IP dest matches masterkrweb. 6-pkg @demica canary campaign.
On install, the package's postinstall hook (node canary.js postinstall per package.json) issues an unconditional HTTP GET to bare IP 157.230.17.236:80 at path /dc with query params containing the package name, version, a nonce, and the lifecycle phase. No environment variables, filesystem contents, or credentials are read or transmitted; the payload is limited to package metadata. The README describes this as an authorized dependency-confusion canary against the @demica scope. The fact-of-install ping is otherwise benign, but it performs unconsented outbound network at install time, the destination is a bare IP over cleartext HTTP with no authentication or pinning, and the same postinstall hook is a position from which a future republish could deliver arbitrary payloads. Routing to human review so the @demica organization can confirm the canary is theirs and that the destination IP is operator-controlled.
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
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @demica/shared (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @demica/shared across your stack and pipelines.
If you installed it — respond
@demica/shared 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 @demica/shared 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 @demica/shared 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
- SafeDep · finder
Detect & block this
O3 blocks @demica/shared-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.