Which versions of ded-ps-ded-ps-core are malicious?

The following npm versions of ded-ps-ded-ps-core are flagged malicious: 35.9.1. Treat any of these as compromised.

How do I remediate ded-ps-ded-ps-core if I installed it?

ded-ps-ded-ps-core is a typosquat — you almost certainly intended a legitimately-named package. Remove ded-ps-ded-ps-core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If ded-ps-ded-ps-core 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.

Is ded-ps-ded-ps-core part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-ps-ded-ps-core (version 35.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-ps-ded-ps-core across your stack and pipelines.

Malicious package

ded-ps-ded-ps-corenpm

ded-ps-ded-ps-core is a confirmed malicious npm package (MAL-2026-12673) that typosquats a legitimate package to trick installs (malicious version 35.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ded-ps-ded-ps-core (npm)

MAL-2026-12673

Immediate action

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

npm uninstall ded-ps-ded-ps-core

What this malware does

On require(), index.js loads init.js, which selects a platform-specific endpoint and fetches an opaque native binary from Cloudflare Workers hosts whose names are assembled at runtime by joining split string fragments (e.g. oob-worker.cf1-01-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT covert-channel fallback to base64-chunked subdomains of wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched binary is written to /tmp/.cache<hex> on Unix or %TEMP%/dotnet_diag_<hex>.exe on Windows — filenames chosen to mimic hidden cache and.NET diagnostics artifacts — then chmod 0755 and spawned detached via /bin/sh -c or cmd.exe start /b. lib/telemetry.js additionally constructs sensitive API names at runtime (require("child_" + "process"), fs["chmod" + "Sync"]) to evade static analysis. Requiring the package causes arbitrary attacker-controlled native code to execute on the installer's host.

Malicious versions

1 flagged

35.9.1

Indicators of compromise (SHA-256)

cfe3941502d9792a1ad46ba7ed447227ef74d1c45cce8e9996005218d47f0f51

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-ps-ded-ps-core (version 35.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-ps-ded-ps-core across your stack and pipelines.
If you installed it — respond
ded-ps-ded-ps-core is a typosquat — you almost certainly intended a legitimately-named package. Remove ded-ps-ded-ps-core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ded-ps-ded-ps-core 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 ded-ps-ded-ps-core 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

No. ded-ps-ded-ps-core on npm has been identified as a malicious package (version 35.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015103

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ded-ps-ded-ps-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