Public mode

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

Some sources or documents need attention: 275/275 feeds/APIs · 469/469 docs · 9/9 advisories · checked 06:21 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in @ecg-internal/adobe-dmp-js (npm)

Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.

osv · MAL-2026-18206

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8a24a1672f5d2075c0159dee85aaad5dcb27d0cdc7eb6e007bfdbb742b82149f) Package uses the `@ecg-internal/*` scope (resembling an internal namespace) and ships a minimal stub whose only effect is to beacon host identifiers to a hardcoded bare-IP endpoint. `package.json` declares a `postinstall` that runs `beacon.cjs`, which POSTs JSON containing `os.hostname()`, `__dirname` (install path), `process.cwd()`, Node version, and the package name to `http://185.158.107.175:8787/_ah/dc` over plain HTTP. The package `main` (`index.js`) also calls `require('./beacon.cjs').fire()` at top level, so the same callback fires on every `require`/`import`. `index.js` exports a `Proxy` no-op so property accesses on the module silently return functions, allowing consumer build pipelines to continue without errors and masking that the package is a stub. The hardcoded bare-IP destination over plain HTTP, unrelated to any legitimate Adobe or ECG infrastructure, together with the internal-looking scope and inert functional surface, is the canonical dependency-confusion reconnaissance payload used to map which victims resolved an attacker-published public package in place of a private internal one. ## Source: ghsa-malware (129bfdb7d01fac087cf552c1da7cf53197ddf37159ca4dd8d73f6d8b1fe87d50) 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
23 Oct 2026 01:58:53 UTC
Source modified
23 Oct 2026 02:45:05 UTC
Observed 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

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.

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 8 Nov 06:21 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current