Skills/ClawHub/funding-rate-trader

funding-rate-trader@1.0.1

CAUTION· install only

Publisher claims: "Crypto funding rate arbitrage strategy. Scan negative funding rates, auto-trade with stop-loss/take-profit. No API key needed for scanning, Binance API for t..." Observed in sandbox: sends data to fapi.binance.com.

Registry ClawHubPublisher dagangtj · publishing for 267 daysInstalls 1,880Last detonated 42 min ago

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
5 of 5 bundled scripts 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 72/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: sends data to fapi.binance.com.

Behavior trace

Honeypot run · 0 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessexited 1: Node.js v22.23.5
0.2sprocessbundled script run in the sandbox with no arguments
0.3snetworkCONNECT tcp://fapi.binance.com:443 · not in the allow-list, refused
0.3sprocessexited 1: Node.js v22.23.5
0.3sprocessbundled script run in the sandbox with no arguments
0.4sprocessexited 1: Node.js v22.23.5
0.4sprocessbundled script run in the sandbox with no arguments
0.5sprocessexited 1: Node.js v22.23.5
0.5sprocess5 of 5 bundled scripts run with no arguments
0.5sprocessscript backend runs setup only
0.5sprocessscript backend runs setup only
0.5sprocessno install scripts to re-run

Static findings

No findings across 410 lines in 7 files.

Cost to the agent

Instructions loaded
≈359 tok
1 file · 7 in bundle

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

8 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
  2. Unclaimed publisher≈ +8 on the totalClaim dagangtj: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim dagangtjPropose a patch to the maintainer