Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent PowPow account-registration helper, with expected but sensitive temporary handling of account and login-token data.
Install only if you want an agent to help create a PowPow account. Expect it to send your registration details to PowPow, temporarily store a login token in the system temp directory, generate one-click login links containing that token, and optionally create payment checkout files. Do not share generated login links, do not provide payment credentials to the agent, and run the provided cleanup command when finished.
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
Referenced artifact was not completely inspected
- Babban script ɗin `scripts/powpow-register.mjs`: **ba shi da dogaro**, yana buƙatar **Node >= 18**. Kafin ka fara, ka gudanar da `node scripts/powpow-register
The entire skill description is written in Hausa and does not indicate that other languages are supported or that the user can choose their preferred language. Under the stated policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale restriction is explicitly documented and justified.
The markdown instructs the agent to continue in a specific 'PowPow' style and prescribes fixed phrasing patterns for responses. This imposes a language/locale-style constraint on all interactions without indicating that the user can choose a different language or communication style.
The manifest sets a single language value of "ha", which indicates the skill is constrained to Hausa. Under the policy, forcing a specific language without user opt-in or a clearly documented justification is a natural-language policy violation.
SQP-3 applies to all file types and covers language/locale policy violations. The error-handling guidance includes Chinese-only error strings such as "Node 版本过低" and "用户名已存在" without any opt-in or explicit justification for forcing those languages, which could impose a language constraint on users or operators.
This markdown file contains natural-language instructions in Hausa but also hard-codes user-facing success text in Chinese ("支付成功"). Elsewhere it references fixed English strings shown to users, without indicating that the user can choose their preferred language or locale, which may violate language/locale policy.
SQP-3 applies to all file types and covers language or locale policy violations. This markdown file presents the skill guidance in a fixed language/locale, and quoted UI/error strings are also fixed-language, with no indication that users can opt into this language or that the skill is intentionally region-specific.
The entire instruction file is written in Hausa and provides no indication that language is optional, user-selected, or constrained for a documented regional reason. This may violate the language/locale policy criterion when a skill implicitly forces a specific language without user opt-in.
The file instructs the agent to send packaged screenshots directly to users and only discusses availability, not whether the images may expose personal data, account details, or other sensitive UI content. Even if these appear to be product screenshots, normalizing unconditional image sharing without a privacy check can lead to unintended disclosure if screenshots later contain real user data or internal-only interface details.
The script persists a live session JWT token to a predictable file in the system temp directory. Even with file mode 0600, storing bearer tokens on disk increases the chance of local compromise through other local processes running as the same user, temp-directory scraping, backups, or delayed cleanup; anyone who obtains the token can act as the user without knowing the password.
The file specifies that users will see the English text "You're All Set!" on the membership page, but does not mention any localization choice or consent. Requiring a fixed language for user-facing content without opt-in can be a policy issue.
The file header says the state file stores email, username, nickname, JWT token, order number, and steps, and that cleanup removes the token at flow end. However, the implementation only removes the token from the status display, not from the underlying state except on explicit cleanup, so the documentation implies stronger lifecycle handling than the code enforces. This is a documentation-to-code mismatch about credential handling intent.
The script writes server-returned payment page content to a temporary local HTML file for browser use. While the success message mentions that a payment page was generated, there is no explicit warning before the write that local files will be created in the temp directory.
This code creates a temporary HTML file that redirects the user to PayPal. The operation affects the local filesystem, but the write itself is not accompanied by a direct warning that a temp file is being created and may persist locally.