OlaXBT Nexus Data

ReviewAudited by ClawScan on May 1, 2026.

Overview

This appears to be a coherent crypto data API wrapper, but it requires a wallet-linked API token, so users should protect the token and keep API endpoints trusted.

Before installing, verify the package source, set NEXUS_JWT only in a trusted environment, leave API URLs at their defaults unless you trust the override, and avoid sharing logs or screenshots that may contain token data.

Findings (5)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

API calls made with this token may access the user's Nexus account data or consume account/API credits.

Why it was flagged

The skill requires a wallet-linked bearer token for API access. This is expected for the stated service, but it gives the skill authenticated account/API authority.

Skill content
| `NEXUS_JWT` | Bearer token for the Nexus data API. Obtain it via the auth flow
Recommendation

Use a revocable token, scope it if the service supports scoping, keep it out of shared logs, and rotate or revoke it if exposed.

What this means

A shared console log or screenshot could reveal part of a sensitive authentication token.

Why it was flagged

The example prints the beginning of the JWT to stdout. This is user-directed example code rather than hidden exfiltration, but token fragments can still appear in terminal logs or screenshots.

Skill content
print(f"   JWT Token: {jwt_token[:50]}...\n")
Recommendation

Avoid printing token material; redact this line before using the example in shared terminals, CI logs, demos, or screenshots.

What this means

If those environment variables are set incorrectly or maliciously, authenticated requests could go to an unintended endpoint.

Why it was flagged

The client can be pointed to alternate API base URLs via constructor arguments or environment variables. This is disclosed configuration behavior, but a bad override could redirect JWT-authenticated requests.

Skill content
self.auth_url = auth_url or os.getenv("NEXUS_AUTH_URL", "https://api.olaxbt.xyz/api")
self.data_url = data_url or os.getenv("NEXUS_DATA_URL", "https://api-data.olaxbt.xyz/api/v1")
Recommendation

Leave the default OlaXBT endpoints unless you intentionally need an override, and only use trusted HTTPS URLs.

What this means

A future install may resolve to different dependency versions than the reviewed package used.

Why it was flagged

The package uses dependency ranges rather than pinned versions. This is common for Python libraries, but installed dependency versions can vary over time.

Skill content
dependencies = [
    "web3>=6.0.0",
    "requests>=2.28.0",
    "pydantic>=2.0.0",
    "cryptography>=42.0.0",
    "python-dotenv>=1.0.0",
]
Recommendation

Install from the official source, prefer a lockfile or pinned versions in production, and review package provenance before use.

What this means

Users might overestimate how protected the JWT is during local use.

Why it was flagged

The changelog makes strong security claims. The provided main client configuration also shows JWT encryption disabled, so users should treat these claims as marketing rather than a reason to handle the token casually.

Skill content
- JWT token encryption in memory
- Military-grade encryption for sensitive data
Recommendation

Treat NEXUS_JWT like any other bearer secret: store it securely, avoid exposing it in logs, and rotate it if compromised.