What does the dlp-dlp-core malware do?

On `require('dlp-dlp-core')`, index.js loads setup.js which selects a platform-specific path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), downloads bytes over HTTPS from string-obfuscated Cloudflare Workers mirrors (oob-worker.cf102-baf.workers.dev, cf103-070, cf100-416, cf99-9b3.workers.dev), writes them to /var/tmp/.cache_ or Temp/dotnet_diag_ .exe, chmods 0755, and detached-spawns them via `spawn('/bin/sh', ['-c', filePath + ' &'], {detached: true})` or `spawn('cmd',...)`. A fallback covert-retrieval channel uses DNS TXT lookups against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, reassembling base64 chunks and executing the result

Which versions of dlp-dlp-core are malicious?

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

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

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

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

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

Malicious package

dlp-dlp-corenpm

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

Malicious code in dlp-dlp-core (npm)

MAL-2026-13278

Immediate action

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

npm uninstall dlp-dlp-core

What this malware does

On require('dlp-dlp-core'), index.js loads setup.js which selects a platform-specific path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), downloads bytes over HTTPS from string-obfuscated Cloudflare Workers mirrors (oob-worker.cf102-baf.workers.dev, cf103-070, cf100-416, cf99-9b3.workers.dev), writes them to /var/tmp/.cache_<hex> or Temp/dotnet_diag_<hex>.exe, chmods 0755, and detached-spawns them via spawn('/bin/sh', ['-c', filePath + ' &'], {detached: true}) or spawn('cmd',...). A fallback covert-retrieval channel uses DNS TXT lookups against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, reassembling base64 chunks and executing the result. Network destinations, DNS domains, and the child_process module name are constructed via array-split/join to evade static analysis; the dropped file paths use cover names (dotnet_diag,.cache_,.analytics_state). lib/telemetry.js (81KB) ships a second copy of the downloader/executor with the same shape. The package's stated purpose ("base framework module / foundational types") does not correspond to any code in the tarball; the entire codebase is fetch-and-execute scaffolding. Env-var opt-outs (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) provide a telemetry cover story.

Malicious versions

1 flagged

35.1.3

Indicators of compromise (SHA-256)

6a7f83a18ee0f4d41331997bd85740febbb8d8e581fa9026b83112e55d2b8320

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 dlp-dlp-core (version 35.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dlp-dlp-core across your stack and pipelines.
If you installed it — respond
Remove dlp-dlp-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 dlp-dlp-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 dlp-dlp-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. dlp-dlp-core on npm has been identified as a malicious package (version 35.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015711

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dlp-dlp-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