Which versions of dpdgroup-css are malicious?

The following npm versions of dpdgroup-css are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate dpdgroup-css if I installed it?

dpdgroup-css 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 dpdgroup-css — how do I know if it already compromised me?

If dpdgroup-css 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 dpdgroup-css part of a known attack campaign?

Yes — dpdgroup-css is associated with the IN-MAL-2026-016757 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 dpdgroup-css across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dpdgroup-css (version 2.0.1).

Malicious package

dpdgroup-cssnpm

Advisory published Aug 6, 2026Updated Aug 6, 2026

dpdgroup-css is a confirmed malicious npm package (MAL-2026-13444) that opens a backdoor for remote access (malicious version 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dpdgroup-css (npm)

MAL-2026-13444

Immediate action

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

npm uninstall dpdgroup-css

What this malware does

package.json declares both preinstall and postinstall lifecycle hooks that run node setup.js on every npm install. setup.js reads the installer's machine hostname via os.hostname() and issues an HTTP GET to a hardcoded bare-IP callback at http://89.116.25.133:4444/dpdgroup-css/<hostname>, with the hostname also carried in an X-PoC-Host header. The package name dpdgroup-css resembles an internal scope for the DPDgroup courier organization, consistent with a dependency-confusion attack: a private build that resolves this public version instead of an intended internal package auto-runs the beacon and discloses the internal build-host identifier to an external, non-first-party bare-IP endpoint. No legitimate library functionality is present.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

30c55e6b20286d3fc29d7c3bc24932180a5e94a6fe5147393d91da212fc0dc10

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for dpdgroup-css (version 2.0.1).
If you installed it — respond
dpdgroup-css 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 dpdgroup-css 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. dpdgroup-css on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016757

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dpdgroup-css-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