Which versions of dc-dc-core are malicious?

The following npm versions of dc-dc-core are flagged malicious: 35.3.3. Treat any of these as compromised.

How do I remediate dc-dc-core if I installed it?

Remove dc-dc-core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed dc-dc-core — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for dc-dc-core (version 35.3.3).

Malicious package

dc-dc-corenpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

dc-dc-core is a confirmed malicious npm package (MAL-2026-12670) that executes malicious code on install (malicious version 35.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dc-dc-core (npm)

MAL-2026-12670

Immediate action

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

npm uninstall dc-dc-core

What this malware does

On require('dc-dc-core'), index.js loads support.js which fetches a platform-specific native binary from obfuscated Cloudflare worker hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to a temp path under a disguised name (dotnet_diag.exe on Windows,.cache_ on Unix), chmods 0755, and spawns it detached via child_process.spawn (spawn('/bin/sh',...) or spawn('cmd',...)). A DNS-TXT fallback channel reassembles a payload by querying resolver domains sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru. Hostnames are constructed by joining split string fragments at runtime to evade static detection, and the module wraps the behavior in analytics/telemetry cover-story naming (DISABLE_TELEMETRY env gate, /tmp/.analytics_state TTL flag). The package name resembles legitimate scopes but ships an import-time dropper.

Malicious versions

1 flagged

35.3.3

Indicators of compromise (SHA-256)

e706ce5be3f3c1cf779ad16844cea8737714c708fe739316bec4ff400b415139

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dc-dc-core (version 35.3.3).
If you installed it — respond
Remove dc-dc-core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dc-dc-core 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. dc-dc-core on npm has been identified as a malicious package (version 35.3.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015112

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dc-dc-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database