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

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

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

Remove ded-ps-events-ded-ps-events-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 ded-ps-events-ded-ps-events-core — how do I know if it already compromised me?

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

Yes — ded-ps-events-ded-ps-events-core is associated with the IN-MAL-2026-015099 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-events-ded-ps-events-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-events-ded-ps-events-core (version 35.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-ps-events-ded-ps-events-core across your stack and pipelines.

Malicious package

ded-ps-events-ded-ps-events-corenpm

ded-ps-events-ded-ps-events-core is a confirmed malicious npm package (MAL-2026-12674) that executes malicious code on install (malicious version 35.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12674

Immediate action

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

npm uninstall ded-ps-events-ded-ps-events-core

What this malware does

index.js unconditionally requires./setup.js on load. setup.js assembles hostnames at runtime via Array.join("") to hide them from static scanners, resolving to four Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. It selects a platform-specific path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), downloads the binary over HTTPS, writes it to /var/tmp or the Windows temp directory under a disguised name (dotnet_diag_<hex>.exe or.cache_<hex>), chmods 0o755, and spawns it detached via /bin/sh -c or cmd with.unref(). No hash or signature verification is performed, the endpoints are unrelated to the package's stated purpose (an event-bus framework), and a cooldown flag is written for persistence. Importing this package auto-executes attacker-controlled native code on the installer's machine.

Malicious versions

1 flagged

35.4.2

Indicators of compromise (SHA-256)

38b1237ac35f64b35ae902019d79b84aeb8eacafc07339fcbca0de866dc6b797

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-ps-events-ded-ps-events-core (version 35.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-ps-events-ded-ps-events-core across your stack and pipelines.
If you installed it — respond
Remove ded-ps-events-ded-ps-events-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 ded-ps-events-ded-ps-events-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-events-ded-ps-events-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-events-ded-ps-events-core on npm has been identified as a malicious package (version 35.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015099

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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