registry / AI-agent control-surface risk / @adrianfathurs/plugin-agent-tracker
@adrianfathurs/plugin-agent-tracker
NPM package to record AI prompting and dev activity into Mandays telemetry backend.
This report shows the evidence for @adrianfathurs/plugin-agent-tracker@1.0.2. 1 of 5 known versions is blocked or flagged. The newest version, 1.0.4, is flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe postinstall lifecycle hook automatically writes a prompt-triggered command into the user-wide Claude Code configuration without affirmative consent. This meets the policy for blocking unconsented install-time mutation of a foreign AI-agent control surface.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Installing the package with npm, followed by a Claude Code prompt submission.
Impact
Installation changes a global AI-agent control surface without affirmative consent and enables recurring telemetry calls when prompts are submitted.
Mechanism
The postinstall script writes a UserPromptSubmit hook to ~/.claude/settings.json, where it invokes the package CLI. The CLI calls the telemetry client.
Policy narrative
During npm postinstall, the package registers a command in the user's global Claude Code settings without asking for consent. The command runs on each prompt submission and sends project and agent identifiers to the configured telemetry endpoint. This is an unconsented install-time change to a foreign AI-agent control surface.
AI rationale
The postinstall lifecycle hook automatically writes a prompt-triggered command into the user-wide Claude Code configuration without affirmative consent. This meets the policy for blocking unconsented install-time mutation of a foreign AI-agent control surface.
Evidence
package.jsondist/setup-hooks.jssrc/setup-hooks.tsdist/cli.jsdist/index.js~/.claude/settings.json
Network endpoints1
localhost:3000/agents/telemetry
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 98.0% confidence with low false-positive risk.
Evidence for policy risk
- The package runs dist/setup-hooks.js automatically during postinstall.
- The installer edits the user-wide ~/.claude/settings.json file and adds a UserPromptSubmit command hook without a consent check.
- That hook runs the package CLI whenever the user submits a prompt; the CLI sends project and agent identifiers to the telemetry endpoint.
- The telemetry client defaults to http://localhost:3000 and allows its destination to be configured.
Evidence against
- The inspected telemetry request sends project and agent identifiers, prompt count, and duration; the cited request body does not show prompt text.
- The destination defaults to localhost and can be supplied through configuration or an environment variable.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node dist/setup-hooks.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg11"build": "tsc && chmod +x dist/cli.js dist/setup-hooks.js",
"postinstall": "node dist/setup-hooks
High
Suspicious Lifecycle Evidence
The package runs dist/setup-hooks.js automatically during postinstall.
package.jsonView on unpkg · L11dist/setup-hooks.jsView file
32function setupClaudeCodeHook() {
L33: const claudeConfigDir = node_path_1.default.join(node_os_1.default.homedir(), '.claude');
L34: const settingsPath = node_path_1.default.join(claudeConfigDir, 'settings.json');
...
L41: catch {
L42: console.warn('⚠️ [Agent Tracker] ~/.claude/settings.json bukan JSON valid, dilewati.');
L43: return;
...
L61: if (!node_fs_1.default.existsSync(claudeConfigDir)) {
L62: node_fs_1.default.mkdirSync(claudeConfigDir, { recursive: true });
L63: }
L64: node_fs_1.default.writeFileSync(settingsPath, JSON.stringify(settings, null, 2));
L65: console.log('✅ [Agent Tracker] Hook UserPromptSubmit terpasang di ~/.claude/settings.json');
L66: }
Findings
1 Critical4 High3 Medium4 Low
CriticalAi Agent Control Hijackdist/setup-hooks.js
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltadist/cli.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencedist/setup-hooks.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @adrianfathurs/plugin-agent-tracker@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @adrianfathurs/plugin-agent-tracker@1.0.2. 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.