T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/vault.py:374- Finding
Workspace audit silently reads credential-bearing files from the user's home directory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This credential-auditing skill is mostly purpose-aligned, but it reads sensitive user-level files and includes under-documented remediation commands that can change or move files beyond what users would reasonably expect.
Review before installing. Use scan-only commands first, preferably in a constrained workspace. Avoid protect, fix-permissions, quarantine, and unquarantine until the package clearly documents them, adds explicit consent, blocks symlinks and path traversal, and requires opt-in before reading home-directory history or shell configuration files.
scripts/vault.py:374Workspace audit silently reads credential-bearing files from the user's home directory
scripts/vault.py:1029Untrusted quarantine metadata can restore and overwrite files outside the workspace
scripts/vault.py:863Under-documented remediation commands can modify or relocate SSH private keys and follow credential-named symlinks
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Why This Matters
Credentials don't just leak through source code. They leak through:
- **Permissions** — .env files readable by every user on the system
- **Shell history** — passwords and tokens visible in `.bash_history`
- **Git config** — credentials embedded in remote URLs
- **Config files** — hardcoded secrets in JSON/YAML/TOML/INI configs
The skill reads shell history and shell configuration files from the user's home directory, which exceeds the stated workspace-scoped behavior and grants access to highly sensitive data outside the project. Those files commonly contain plaintext credentials, tokens, internal hostnames, and command history unrelated to the workspace, so this broadens data access significantly.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Credential file names
CREDENTIAL_FILES = {
".env", ".env.local", ".env.production", ".env.staging", ".env.development",
".env.test", ".env.ci",
"credentials.json", "service-account.json", "secrets.json",
".npmrc", ".pypirc", ".netrc", ".pgpass", ".my.cnf",
No suspicious patterns detected.