pintumcp@1.2.7
Agent Alerts MCP — desktop notifications with sound for AI coding agents
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall path automatically modifies AI agent configurations and installs Claude Code hooks without consent. This meets the blocking policy for unconsented install-time mutation of agent control surfaces.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
npm installation runs the package’s postinstall hook.
Impact
The changes enable the package’s server and hook commands to run through configured AI tools.
Mechanism
The hook invokes the install command, which writes MCP configuration entries for detected tools and adds Claude Code command hooks.
Policy narrative
The postinstall hook automatically starts setup. Setup detects available AI coding tools, writes the package’s MCP configuration into their settings, and adds Claude Code hooks without asking for consent. This is an active install-time mutation of AI agent control surfaces.
AI rationale
The postinstall path automatically modifies AI agent configurations and installs Claude Code hooks without consent. This meets the blocking policy for 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 99.0% confidence with low false-positive risk.
Evidence for policy risk
- The package runs install.js from its postinstall hook, which automatically invokes the install command.
- That command configures detected agent tools and adds Claude Code hooks during the install flow, without a consent check.
- The configuration code writes the package’s MCP entry into each detected tool’s configuration.
- The Claude hook code adds commands for prompt, notification, and stop events to the user’s settings.
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": [
High
Suspicious Lifecycle Evidence
The package runs install.js from its postinstall hook, which automatically invokes the install command.
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/tray_cross.pyView file
Findings
5 High4 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similaritybin/pintumcp.js
HighKnown Malware Source Fingerprint Signaturebin/pintumcp.js
HighPrevious Version Dangerous Deltabin/pintumcp.js
HighSuspicious Lifecycle Evidencepackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helperpython/tray_cross.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to pintumcp@1.2.7.
See all versions of pintumcp for other recorded verdicts.
- Avoid installing pintumcp@1.2.7. 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.