If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (452b525d6d3fc409e081d5f8a6f052c7b3b9899d1f088a24d93e4be4de65c9cf)
The package's index.js reads installer-owned secret files from the home directory (~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.ssh/config, ~/.aws/credentials, ~/.npmrc, ~/.gitconfig,.env variants, secrets.json, credentials.json), enumerates process.env for keys matching sensitive keywords (API, KEY, SECRET, TOKEN, PASS, AWS, GITHUB, SLACK, WEBHOOK, AUTH, CERT, PRIVATE), and walks the working directory for.env/.js/.json config, secret, key, and credential files. The collected data is base64-encoded and POSTed to a hardcoded Burp Collaborator (oastify.com) subdomain along with os.hostname() and os.userInfo() identifiers. package.json wires this payload to run automatically via both preinstall and postinstall lifecycle hooks ("node index.js"), and index.js also invokes executePayload() at top level so require() triggers the same behavior. No legitimate functionality is present.
Source: ossf-package-analysis (99169ee1ec0063106ed3fca297363e799a07a85ec07190e20fd86a9ba3339ce6)
The OpenSSF Package Analysis project identified 'dlab_workshop' @ 1.0.7 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.