cktool-core
⚠️ SECURITY RESEARCH — Apple Bug Bounty dependency confusion PoC. The correct package is @apple/cktool.core.
This report shows the evidence for cktool-core@1.0.1. 5 of 6 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms a lifecycle-triggered dependency-confusion PoC with external install pingback and persistent identifier, which is concrete unconsented behavior even though it does not steal secrets. This should be blocked as dependency-confusion telemetry rather than treated as scanner noise.
Decision evidence
public snapshot- package.json runs postinstall: node postinstall.js
- postinstall.js executes at install time and sends HTTPS POST to npx-monitor-76056.azurewebsites.net/api/pingback
- postinstall.js creates/reads a persistent install ID in XDG_CACHE_HOME or ~/.cache/.cktool-core-id
- Payload includes install ID, package version marker, npm-postinstall marker, and timestamp
- README describes this as dependency confusion PoC for unscoped cktool-core vs @apple/cktool.core
- index.js only prints warning/remediation text when imported or run
- No credential file harvesting, shell execution, eval, native binary loading, or AI-agent control-surface writes found
- Network payload is limited to install telemetry, not source files or secrets
Source & flagged code
2 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to cktool-core@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing cktool-core@1.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.