registry / AI-agent control-surface risk / @lovrabet/lovrabet-cli
@lovrabet/lovrabet-cli
Runtime CLI for Lovrabet apps, datasets, SQL, Backend Function, skills, and AI agent workflows.
This report shows the evidence for @lovrabet/lovrabet-cli@2.3.3. 2 of 17 known versions are blocked or flagged. The newest version, 2.3.5, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an unconsented postinstall mutation of broad AI-agent control surfaces, with remote npx execution and deliberate obfuscation. It meets the install-hook abuse block boundary.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm installation, via postinstall
Impact
It can alter the user-wide control surface of .agents and .claude without an explicit setup command.
Mechanism
Obfuscated postinstall launches npx skills@latest to add a global AI-agent skill
Policy narrative
During npm installation, package.json starts scripts/postinstall.mjs. That script dynamically imports the obfuscated postinstall module, which calls an npx command for the mutable skills@latest package and requests global skill installation. The bundled installer checks global .agents and .claude skill paths, so the lifecycle hook changes broad AI-agent configuration rather than limiting work to this CLI's package directory. The code is deliberately obfuscated, reducing transparency for an automatic privileged action.
AI rationale
This is an unconsented postinstall mutation of broad AI-agent control surfaces, with remote npx execution and deliberate obfuscation. It meets the install-hook abuse block boundary.
Evidence
package.jsonscripts/postinstall.mjs.agents/skills/lovrabet/SKILL.md.claude/skills/lovrabet/SKILL.md.agents/.skill-lock.json
Network endpoints1
registry.npmjs.org
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 a postinstall hook automatically.
- The hook dynamically imports and runs the packaged postinstall module.
- The installed code invokes npx with skills@latest to add a global skill.
- It targets broad AI-agent skill locations including .agents and .claude.
- The published build deliberately obfuscates the runtime code.
Evidence against
- No self-dependency chain is declared.
- The update command is user-invoked rather than install-time.
Behavioral surface
CryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedObfuscatedUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgscripts/postinstall.mjsView file
17try {
L18: const { runPostinstall } = await import(pathToFileURL(entry).href);
L19: await runPostinstall();
Medium
Dynamic Require
Package source references dynamic require/import behavior.
scripts/postinstall.mjsView on unpkg · L17Findings
4 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSame File Env Network Executionlib/commands/update.js
HighObfuscated Payload Loaderlib/generated/official-routing.js
HighObfuscated
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirescripts/postinstall.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @lovrabet/lovrabet-cli@2.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lovrabet/lovrabet-cli@2.3.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.
Versions
17 known versions2.3.5latestSuspiciousAgent extension lifecycle riskWarnPublishedOct 16, 2026, 6:31 AM2.3.4SuspiciousAgent extension lifecycle riskWarnPublishedSep 24, 2026, 5:35 AM2.3.3shownMaliciousSoft block: AI-agent control surfaceBlockPublishedSep 14, 2026, 3:42 AM2.3.2SuspiciousAgent extension lifecycle riskWarnPublished