near-getpay@1.0.0
CAUTION· install onlyPublisher claims: "Accept crypto payments (NEAR, USDC, USDT) via a beautiful payment page with PingPay or HOT PAY integration." Observed in sandbox: reads credential files.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 1 of 1 bundled script run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 73/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: reads credential files.
Behavior trace
Honeypot run · 4 s · 2 scenariosStatic findings
dotenv.config({ path: path.join(__dirname, '.env') });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.cp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Copy each `item_id` and add to `.env`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.dotenv.config({ path: path.join(__dirname, '.env') });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Add to `.env`: `PINGPAY_API_KEY=your_key_here`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.throw new Error('PINGPAY_API_KEY not configured in .env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<strong>5.</strong> Add to your <code>.env</code> file:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.throw new Error('PINGPAY_API_KEY not configured in .env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Create .env file with:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Copy `.env.example` to `.env`:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Copy .env.example to .env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<strong>4.</strong> Add to your <code>.env</code> file:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Run: `ssh-keygen -t rsa -b 2048 -f ~/.ssh/id_rsa -N ""`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.throw new Error('PINGPAY_API_KEY not configured in .env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.error('❌ PINGPAY_API_KEY not found in .env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.dotenv.config({ path: path.join(__dirname, '.env') });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(output);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."Configure provider credentials in .env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(output);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
7 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Reads credential files≈ +27 on the totalThe sandbox saw reads under ~/.ssh, ~/.aws, ~/.npmrc, ~/.config or similar. Read only files inside the project, and only the ones the task needs. Seen: ~/.npmrc.
- Unclaimed publisher≈ +8 on the totalClaim cuongdcdev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.