Which versions of dlab_workshop are malicious?

The following npm versions of dlab_workshop are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8. Treat any of these as compromised.

How do I remediate dlab_workshop if I installed it?

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.

I already installed dlab_workshop — how do I know if it already compromised me?

If dlab_workshop was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dlab_workshop part of a known attack campaign?

Yes — dlab_workshop is associated with the IN-MAL-2026-015816, IN-MAL-2026-015814, IN-MAL-2026-015788, IN-MAL-2026-015817, IN-MAL-2026-015815, IN-MAL-2026-015789, IN-MAL-2026-015813, IN-MAL-2026-015832 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dlab_workshop across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dlab_workshop (8 malicious versions).

Malicious package

dlab_workshopnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-13277

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dlab_workshop

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

8 flagged

1.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.8

Indicators of compromise (SHA-256)

452b525d6d3fc409e081d5f8a6f052c7b3b9899d1f088a24d93e4be4de65c9cf

b0ffd1e8170d86897e63b8bbbf0da239e1e37fe36aa82a9c1efc2ee79d17c0de

e001fc59e095a26202d9bfc718d60d92129c08ec6631a2fc6808833b7a3f12ac

e702756ab36351254766d24fcdf0fbd44c6e2c5cdef64fff7f52803d3152d7a8

52166d275f134507a38c6e02df1f419e26546e17949881197ac857b8ad249b56

563a21c97425757ea7a1b46024bc73b64da9aca55fe24e0c441c7337e31dcd69

8f5924c4a33a3c26baf58d31eff4233249d3b7746d6d621e54524e6fbb98dd14

99169ee1ec0063106ed3fca297363e799a07a85ec07190e20fd86a9ba3339ce6

82cbfd268ae12212e1c6687b783f1706581fe6998b6c69531c2e116db9137590

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dlab_workshop (8 malicious versions).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dlab_workshop on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015816IN-MAL-2026-015814IN-MAL-2026-015788IN-MAL-2026-015817IN-MAL-2026-015815IN-MAL-2026-015789IN-MAL-2026-015813IN-MAL-2026-015832

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database