me.txt

Security checks across malware telemetry and agentic risk

Overview

This instruction-only skill does what it says: helps create, fetch, and validate public me.txt identity files, with privacy and optional CLI supply-chain cautions.

Install is reasonable if you want help with me.txt files. Do not publish private contact details, exact personal location, secrets, or anything you would not want indexed publicly. Use the npx helper only if you trust the npm package, and avoid the metxt.org fallback for private or sensitive domains.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill instructs the agent to gather and publish personal identity details such as name, links, email, timezone, and communication preferences without any privacy warning or consent checkpoint. In context, this is risky because the output is intended for public web placement, so users may disclose sensitive or correlatable personal data without understanding the exposure.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The GitHub pre-fill instruction directs use of an external CLI (`npx create-me-txt --github username`) without disclosing that profile data will be fetched and processed by third-party code. This creates a transparency and supply-chain risk: users may not realize external tooling is being run or that account-associated data may be transmitted, logged, or enriched beyond what they intended.

Missing User Warnings

Low
Confidence
88% confidence
Finding
The lookup flow includes a third-party fallback service (`metxt.org/api/lookup`) but does not warn that the queried domain will be sent to an external service. While the data shared is limited, this still has privacy and metadata-leak implications, especially for internal, sensitive, or user-supplied domains that should not be disclosed externally.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal