Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in @demica/core (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-5349

Published

Dep-confusion squat of internal @demica/core 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 benign canary" framing does NOT downgrade, raw-IP dest matches masterkrweb. 6-pkg @demica canary campaign. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3abd78892d57868223d66ae70f269e5088d5801f5beaa41418146172a3e5e338) Package self-describes as a dependency-confusion canary targeting the @demica scope and ships a postinstall hook that fires automatically on `npm install`. `package.json` declares `scripts.postinstall: node canary.js postinstall`, and canary.js lines 18-22 issue an HTTP GET to the bare IP 157.230.17.236 on port 80 at path `/dc?...` with the package name, version, a nonce, and the lifecycle phase. Any machine that resolves @demica/[email protected] from the public registry — typically because an internal build accidentally pulled the public squat instead of the private @demica/core — silently announces itself to the operator of 157.230.17.236, disclosing the installer's egress IP, the presence of the @demica internal namespace in the build, and confirmation that the dependency-confusion attack succeeded. The beacon body is metadata-only (no env/filesystem/credential reads), but the install-time outbound HTTP to a hardcoded attacker-controlled bare IP, fired without consent on default install, is the canonical dependency-confusion exploitation primitive and gives the publisher exactly the reconnaissance signal needed to identify and escalate against vulnerable internal build pipelines. ## Source: ghsa-malware (868fdb41b8eb3bf77a844a3c919d8b985ba1c93a1c56e131f970f549d6e516ee) 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.

Source published
9 Jun 2026 07:50:21 UTC
Source modified
13 Aug 2026 22:15:20 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 02:47 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current