@ecg-internal/media-util-js-lib@99.0.1
Compatibility shim.
AI Security Review
scanned 4h ago · by lpm-firewall-aiThe package automatically sends host-identifying metadata to a fixed external collector during installation, with no affirmative consent guard in the inspected source. This is concrete install-time disclosure, so the package should be blocked.
Decision evidence
public snapshot- package.json runs the beacon with a postinstall hook.
- beacon.cjs sends to a fixed external HTTP endpoint.
- beacon.cjs constructs a POST request to that endpoint and writes the request body.
- The beacon payload includes the machine hostname, install path, and working directory.
- The beacon writes the payload and ends the request.
- Importing index.js also calls the beacon.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs the beacon with a postinstall hook.
package.jsonView on unpkg · L7Findings
Affected versions and remediation
This report applies to @ecg-internal/media-util-js-lib@99.0.1.
See all versions of @ecg-internal/media-util-js-lib for other recorded verdicts.
- Avoid installing @ecg-internal/media-util-js-lib@99.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.