registry / makdoong2-team / 1.3.1
makdoong2-team@1.3.1
내 일을 대신해주는 막둥이들. Self-contained opencode plugin for 사내 workflow: per-stage specialist agents, deterministic shell gates, primary-only enforcement, and a model fallback advisor.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source shows guarded, package-owned OpenCode setup, not a verified attack. The automatic lifecycle deployment and broad directory permission grant leave enough residual risk to warn.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
A global npm install, or an install with MAKDOONG2_AUTO_INSTALL=1; CI installs are skipped unless opted in.
Impact
OpenCode receives the plugin and broader file access permissions; source inspection did not establish data theft or another concrete attack.
Mechanism
The hook calls the installer, which copies package-owned agents and skills, registers the plugin, enables its tools, and adds external-directory permissions.
AI rationale
The source shows guarded, package-owned OpenCode setup, not a verified attack. The automatic lifecycle deployment and broad directory permission grant leave enough residual risk to warn.
Evidence
package.jsonpostinstall.mjsscripts/install-lib.mjs
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs a postinstall hook that deploys its plugin when installed globally or when its package-specific opt-in is set.
- That deployment adds the package plugin and enables its tools in the OpenCode configuration.
- The installer grants access to the package and OpenCode configuration directories, leaving a broad permission change that merits review.
Evidence against
- Local installs and CI installs skip deployment unless the package-specific opt-in is set.
- The deployment is first-party plugin setup; inspected behavior does not establish credential theft, unrelated data export, or remote code execution.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/cli.jsView file
16import { dirname, join, resolve } from "node:path";
L17: import { execFileSync } from "node:child_process";
L18: import {
High
3
Findings
1 Critical5 High4 Medium5 Low
CriticalAi Agent Control Hijackscripts/install-lib.mjs
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/cli.js
HighRuntime Package Installbin/cli.js
HighSemantic Analysis Limitedscripts/install-lib.mjs#virtual:normalized:round1
HighKnown Malware Source Similarityskills/bamboo-ci/run-bamboo.sh
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helpergates/stage6-post-commit-verify.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Low
Affected versions and remediation
This report applies to makdoong2-team@1.3.1.
See all versions of makdoong2-team for other recorded verdicts.
- Review the evidence and your use of makdoong2-team@1.3.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.