dlab_workshopnpm
dlab_workshop is a confirmed malicious npm package (MAL-2026-13277) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dlab_workshop (npm)
What this malware does
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dlab_workshop (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dlab_workshop across your stack and pipelines.
If you installed it — respond
dlab_workshop is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dlab_workshop was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dlab_workshop before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks dlab_workshop-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.