engineering-skills

No clear supply-chain malware indicators are present (no obfuscation, no dynamic execution, no suspicious external network exfiltration logic). The primary security concern is credential disclosure: bulk provisioning exports plaintext per-user passwords to a CSV file, creating an at-rest secret exposure risk. Secondary concerns are high-impact privileged operations (Conditional Access policy creation and user/mailbox lifecycle changes) that require strict access control, auditing, and careful use of WhatIf/report-only modes.

This module is primarily a command orchestration catalog for Google Workspace-related CLI operations. It shows no overt malware indicators (no credential theft, exfiltration, persistence, or obfuscation) in the provided fragment. However, it contains a high-impact structural risk: it executes shell command strings via subprocess.run(..., shell=True) sourced from a recipe catalog. If the catalog or missing surrounding code performs placeholder interpolation or can be tampered with, the tool could become an arbitrary command execution vector. Treat as security-sensitive, especially in a supply-chain threat model.

No strong evidence of covert malware (e.g., exfiltration, backdoor/persistence, or obfuscated payloads) is present in the provided fragment. However, the module generates highly privileged Microsoft 365 administration scripts and directly interpolates user-controlled fields into PowerShell code without visible escaping, creating a realistic script/command injection risk if attacker-controlled inputs can reach script generation/execution. It also embeds a weak default initial password pattern, which is an operational security concern. The snippet appears malformed/incomplete, so certainty is limited, but overall security risk remains moderate-to-high due to privileged automation and insecure templating.

SUSPICIOUS: the skill’s purpose and capabilities are coherent for Google Workspace administration, but the install instructions are not. The mismatched npm and Cargo package names materially weaken install trust and could route users to the wrong package, while the rest of the data flows appear proportionate and aimed at official Google Workspace use rather than clear exfiltration.

SUSPICIOUS. The skill’s stated capabilities mostly fit a Playwright testing toolkit, and the referenced external services are legitimate. However, the trust-critical implementation details for the claimed MCP servers and credential handling are missing, so install provenance and exact data flows cannot be verified. This looks coherent but under-specified, with moderate supply-chain and credential-forwarding risk rather than confirmed malware.