Which versions of dp-owners are malicious?

The following npm versions of dp-owners are flagged malicious: 35.2.6. Treat any of these as compromised.

How do I remediate dp-owners if I installed it?

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

I already installed dp-owners — how do I know if it already compromised me?

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

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

Malicious package

dp-ownersnpm

dp-owners is a confirmed malicious npm package (MAL-2026-13200) that typosquats a legitimate package to trick installs (malicious version 35.2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dp-owners (npm)

MAL-2026-13200

Immediate action

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

npm uninstall dp-owners

What this malware does

On require() of dp-owners, init.js selects a platform-specific path, downloads a binary from hardcoded Cloudflare Workers hosts assembled via string-split concatenation (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT chunked-base64 fallback under *.dl.wel1.ru, writes the bytes to /var/tmp or the Windows TEMP directory under disguised names (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods the file 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. Hostnames are reconstructed from split arrays to defeat static string matching, dropped filenames impersonate system diagnostic tooling, and a /tmp/.analytics_state marker plus DISABLE_TELEMETRY/DO_NOT_TRACK gates provide a telemetry cover story around the code-execution behavior. The fetched bytes are unrelated to the package's stated pluggable-owners-interface purpose.

Malicious versions

1 flagged

35.2.6

Indicators of compromise (SHA-256)

09f190519e55e1e9899983a76806e839baf855abf0a0120e83bcac5547405c09

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

Campaign

IN-MAL-2026-015577

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dp-owners-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