VNX-SEC-052: Artifactory / JFrog API key

Reports a JFrog Artifactory API key (AKCp + 69 alphanumerics) or reference token (cmVmd + 59 alphanumerics) as a whole token in any file; lookalikes inside longer base64 runs and placeholders are not reported.

Field	Value
Rule ID	`VNX-SEC-052`
Severity	Critical
SARIF level	`error`
Kind	`secrets`
Languages	Any file
CWE	CWE-798
CAPEC	CAPEC-191
ATT&CK	T1195.002
CWSS vector	`CWSS:1.0/TI:C/AP:A/AL:A/IC:N/FC:LT/RP:N/RL:A/AV:I/AS:N/IN:A/SC:A/BI:C/DI:H/EX:H/EC:N/P:W`
Tags	`secrets` `artifactory` `jfrog` `supply-chain` `credentials`
Source	`internal/sast/rules/vnx-sec-052.rego`

Overview

This rule reports a JFrog Artifactory credential as a whole token: a legacy API key (AKCp followed by 69 letters and digits) or a reference/access token (cmVmd followed by 59 letters and digits). Typical places are .npmrc, gradle.properties, an X-JFrog-Art-Api header or a Bearer header. The prefix inside a longer alphanumeric run (base64 data), shorter lookalikes, placeholder bodies, environment references and test paths are not reported.

What Gets Flagged

//acme.jfrog.io/artifactory/api/npm/npm-virtual/:_password=AKCp<69 characters>

TOKEN = "cmVmdGtuOjAx<52 characters>"

Why This Matters

Hardcoded artifactory / jfrog api key values are routinely scraped by automated bots within minutes of a public push, and then used to access the account, exfiltrate data, or pivot into downstream services. Once the credential is in git history it is permanently in third-party hands.

Remediation

Revoke the leaked credential in the provider’s console immediately.
Replace with a short-lived alternative, OAuth 2.0 access tokens, IAM role assumption, OIDC federation, wherever the platform supports it.
Store the new credential in a secrets manager (AWS Secrets Manager, HashiCorp Vault, GitHub Actions secrets, Doppler).
Audit the provider’s access logs for activity you did not initiate between the leak and the revocation.
Purge from git history with git filter-repo or BFG, then re-scan with gitleaks/truffleHog to confirm no other secrets remain.
Enable push protection so future commits are blocked at the developer machine.

References

CWE-798: Use of Hard-coded Credentials
gitleaks artifactory-api-key, artifactory-reference-token
truffleHog
OWASP Credentials Management Cheat Sheet
MITRE ATT&CK T1552.001 – Credentials In Files
git-filter-repo

Suppressing this rule

Put a nosec comment on the line, or on line 1 to cover the whole file. Use the comment marker of the file’s language (#, //, -- or ;):

# nosec vnx-sec-052
// nosec vnx-sec-052

Or record an ignore rule: vulnetix ignore add --rule vnx-sec-052 --reason "...". See Suppressing findings.