dc-dc-core
core runtime
This report shows the evidence for dc-dc-core@35.3.3, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe import-time, hard-coded remote binary download and detached execution form a concrete arbitrary-code-execution chain; the lack of lifecycle hooks does not mitigate it.
Decision evidence
public snapshot- index.js imports _support.js on every package import.
- _support.js downloads platform binaries from hard-coded hosts.
- DNS TXT fallback reconstructs a binary payload.
- Downloaded bytes are written, chmodded, and detached-spawned.
- package.json has no lifecycle scripts.
- No credential-file harvesting is present in _support.js.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_support.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_support.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to dc-dc-core@35.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing dc-dc-core@35.3.3. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.