cktool-core
Affected
- Versions:
1.0.0,1.0.1,1.0.2,1.0.3,1.0.4
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-qm37-v399-r9m5
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in cktool-core (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (18ee2228fd4f97fcc261019bf662b6e3006a5aed7a6f3bc0ec4fa505a84aa037)
cktool-core is the unscoped public-registry form of the private-scoped @apple/cktool.core package. Installers whose resolver misroutes the scoped name to the public npm registry receive this package instead of Apple's internal library. On install, postinstall.js generates and persists a per-installer UUID under XDG_CACHE_HOME (or ~/.cache) and POSTs it, along with version and timestamp fields, to a hardcoded external endpoint at npx-monitor-76056.azurewebsites.net/api/pingback. The behavior fires unconditionally via the declared postinstall lifecycle hook, so any misresolution results in attacker-controlled JavaScript executing on the installer's machine and an install beacon leaving to a non-vendor destination. The package.json description self-labels this as a dependency-confusion PoC, but the mechanism and installer impact are identical to a real dependency-confusion attack against Apple's private namespace.
Source: ghsa-malware (cdbb75e8b781db493564b5b0bc750b43b94c74909ff0bf5c82271f657e7d2eb2)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0