Back to skill

Security audit

Tmp.Ntdsc1rTS5

Security checks across malware telemetry and agentic risk

Overview

The skill is transparent about querying Credit Karma, but it asks users to expose and replay financial-session cookies and tokens in shell commands, so it needs review before use.

Install only if you are comfortable granting a browser-extension bridge access to your Credit Karma session cookies and handling access and refresh tokens in your shell. Avoid shared machines, shell logging, persistent files, and predictable temp paths; clean up transaction files and revoke/re-login if tokens may have been exposed.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Missing User Warnings

High
Confidence
97% confidence
Finding
The instructions explicitly extract session cookies, split them into access and refresh JWTs, and use them directly in shell variables and HTTP headers. This exposes highly sensitive authentication material for a financial service and provides no warning about account compromise, token leakage via shell history/process inspection, or safe handling requirements.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill writes request and response bodies containing financial transaction data to predictable files under /tmp without warning about local disclosure risk. On multi-user or monitored systems, sensitive transaction data may be exposed through insecure temp-file permissions, backups, forensics, or later accidental reuse.

External Transmission

Medium
Category
Data Exfiltration
Content
"datePeriodInput":{"datePeriod":null},"accountInput":{}}}' \
  '{query:$q, variables:$vars}' > /tmp/ck-body.json

curl -s https://api.creditkarma.com/graphql -X POST \
  -H "Authorization: Bearer $ACCESS" \
  -H 'Content-Type: application/json' \
  -H 'Origin: https://www.creditkarma.com' \
Confidence
95% confidence
Finding
curl -s https://api.creditkarma.com/graphql -X POST \ -H "Authorization: Bearer $ACCESS" \ -H 'Content-Type: application/json' \ -H 'Origin: https://www.creditkarma.com' \ -H 'Referer: https:/

External Transmission

Medium
Category
Data Exfiltration
Content
"datePeriodInput":{"datePeriod":null},"accountInput":{}}}' \
  '{query:$q, variables:$vars}' > /tmp/ck-body.json

curl -s https://api.creditkarma.com/graphql -X POST \
  -H "Authorization: Bearer $ACCESS" \
  -H 'Content-Type: application/json' \
  -H 'Origin: https://www.creditkarma.com' \
Confidence
95% confidence
Finding
https://api.creditkarma.com/

Credential Access

High
Category
Privilege Escalation
Content
`pageInfo.endCursor`, and stop when `pageInfo.hasNextPage` is `false`. See
`references/requests.md` for the full loop.

## Refreshing the access token (no need to re-run `fpx` for this)

The access token is short-lived (~10 min). Refresh with the `refreshToken`
you already extracted — this is a plain `curl`, not another `fpx` capture:
Confidence
98% confidence
Finding
access token

YARA rule 'info_stealer': Information stealer patterns (credential harvesting, browser data theft) [malware]

High
Category
YARA Match
Content
Requirements: the **Transporter** browser extension installed, with an open
`www.creditkarma.com` tab you're signed into, and its Chrome **Site access**
allowing `creditkarma.com`. `CKAT`/`CKTRKID` are `HttpOnly` (invisible to page
JS) but `fpx cookies` reads them via the extension's `chrome.cookies.get`,
same as `@fetchproxy/bootstrap` does inside the MCP. Pairing persists across
invocations.
Confidence
97% confidence
Finding
cookies` reads them via the extension's `chrome

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Static analysis

No suspicious patterns detected.