@ecg-internal/adobe-dmp-js@2.0.1
OpenSSF/OSV Malicious Advisory
imported 3h ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18206 confirms this npm version as malicious.
Advisory
MAL-2026-18206
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @ecg-internal/adobe-dmp-js (npm)
Details
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 & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @ecg-internal/adobe-dmp-js@2.0.1.
The same advisory and Firewall decision cover 5 recorded versions
0.0.1, 1.0.1, 2.0.0, 2.0.1, 99.0.1
See all versions of @ecg-internal/adobe-dmp-js for other recorded verdicts.
- Avoid installing @ecg-internal/adobe-dmp-js@2.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.