Which versions of wp-codebox-workspace are malicious?

The following npm versions of wp-codebox-workspace are flagged malicious: 9999.99.99. Treat any of these as compromised.

How do I remediate wp-codebox-workspace if I installed it?

wp-codebox-workspace establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed wp-codebox-workspace — how do I know if it already compromised me?

If wp-codebox-workspace 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 wp-codebox-workspace part of a known attack campaign?

Yes — wp-codebox-workspace is associated with the IN-MAL-2026-007507 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 wp-codebox-workspace across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wp-codebox-workspace (version 9999.99.99).

Malicious package

wp-codebox-workspacenpm

Advisory published Jun 25, 2026Updated Jun 25, 2026

wp-codebox-workspace is a confirmed malicious npm package (MAL-2026-6458) that opens a backdoor for remote access (malicious version 9999.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wp-codebox-workspace (npm)

MAL-2026-6458

Immediate action

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

npm uninstall wp-codebox-workspace

What this malware does

Package is published at version 9999.99.99 with a description referencing an 'npm 404 error referenced in Extra-Chill/homeboy-extensions' — the textbook dependency-confusion shape, where an unclaimed internal package name is registered publicly at a maximal version so private builds silently resolve to this public package. On install, postinstall.js reads npm package metadata, Node/OS info, and CI environment indicators including GITHUB_REPOSITORY, GITHUB_REPOSITORY_OWNER, and GITHUB_WORKFLOW, then POSTs them to https://ddactic-lab.online/sc/beacon. A DNS-lookup fallback encodes the package slug, CI provider, and a hash into a subdomain label under b.ddactic-lab.online, with an in-source comment stating the channel exists to fire 'even through HTTP-blocking corporate proxies' — explicit intent to evade installer egress controls. The combined effect: any private CI build that mistakenly resolves this name leaks the victim organization's private repository, owner, and workflow identifiers to an attacker-controlled host, with a covert DNS fallback for environments that block HTTP.

Malicious versions

1 flagged

9999.99.99

Indicators of compromise (SHA-256)

a44aa2030ed09d6ec3998c59953a44e013c1993d93a90ee031b0999480afb03c

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for wp-codebox-workspace (version 9999.99.99).
If you installed it — respond
wp-codebox-workspace establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If wp-codebox-workspace 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. wp-codebox-workspace on npm has been identified as a malicious package (version 9999.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007507

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks wp-codebox-workspace-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database