scandoc-scandoc-core
core runtime
This report shows the evidence for scandoc-scandoc-core@20.8.5. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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-aiThis is a concrete import-time staged-payload execution chain unrelated to the documented core-runtime API. Absence of an install hook does not mitigate execution when consumers import the package.
Decision evidence
public snapshot- index.js imports ./_vendor on package import.
- _vendor.js downloads platform payloads from obfuscated worker hosts.
- _vendor.js falls back to DNS TXT payload retrieval.
- _vendor.js writes, chmods, and detached-spawns the payload.
- package.json has no lifecycle scripts.
- Public API wrapper itself is minimal.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L6A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to scandoc-scandoc-core@20.8.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing scandoc-scandoc-core@20.8.5. 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.