pintumcp@1.2.3
Agent Alerts MCP — desktop notifications with sound for AI coding agents
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall automatically runs setup that mutates detected AI-tool configurations and installs Claude Code hooks. This matches the policy for blocking unconsented install-time mutation of agent control surfaces.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing the package through npm, which runs its postinstall hook.
Impact
Installation can change AI-agent configuration and cause Claude Code to run package-provided hook commands.
Mechanism
The hook invokes the CLI install command, which detects tools, configures their MCP settings, and adds Claude Code event hooks.
Policy narrative
The package’s npm postinstall launches its installer without a separate user command. The installer detects local AI tools, configures their MCP entries, and installs Claude Code hooks when the settings directory exists. This is unconsented lifecycle mutation of AI-agent control surfaces.
AI rationale
The postinstall automatically runs setup that mutates detected AI-tool configurations and installs Claude Code hooks. This matches the policy for blocking unconsented install-time mutation of agent control surfaces.
Evidence
package.jsoninstall.jsbin/pintumcp.jslib/configure.jslib/hooks.js
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
- package.json runs install.js automatically during postinstall.
- install.js immediately runs the CLI install command.
- The install command detects installed AI tools and automatically configures each detected tool.
- During that same install command, existing Claude settings trigger automatic hook installation.
- The hooks write command entries for Claude Code events into settings.json.
- The generated local MCP entry invokes the supplied server path and enables the integration.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
HighEntropyStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg9"scripts": {
"postinstall": "node install.js"
},
"keywords": [
"mcp",
"notific
High
Suspicious Lifecycle Evidence
package.json runs install.js automatically during postinstall.
package.jsonView on unpkg · L9•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpython/server.pyView file
•
Findings
5 High4 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltabin/pintumcp.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidenceinstall.js
HighAi Review Evidencebin/pintumcp.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helperpython/server.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to pintumcp@1.2.3.
See all versions of pintumcp for other recorded verdicts.
- Avoid installing pintumcp@1.2.3. 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.