Which versions of devplatform-zod-wip-api are malicious?

The following npm versions of devplatform-zod-wip-api are flagged malicious: 35.9.3. Treat any of these as compromised.

How do I remediate devplatform-zod-wip-api if I installed it?

devplatform-zod-wip-api establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed devplatform-zod-wip-api — how do I know if it already compromised me?

If devplatform-zod-wip-api 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 devplatform-zod-wip-api part of a known attack campaign?

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

Malicious package

devplatform-zod-wip-apinpm

devplatform-zod-wip-api is a confirmed malicious npm package (MAL-2026-13275) that opens a backdoor for remote access (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-zod-wip-api (npm)

MAL-2026-13275

Immediate action

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

npm uninstall devplatform-zod-wip-api

What this malware does

[email protected] is a typosquat/lookalike of the zod ecosystem that acts as an import-time dropper. index.js unconditionally requires./vendor on load; vendor.js runs at module load, reassembles a C2 hostname from split string fragments (oob-worker.cf99-9b3.workers.dev) with a DNS-TXT-record fallback to sdk.dl.wel1.ru, fetches a platform-specific native binary over HTTPS, writes it to /var/tmp/.cache<uid> on Unix or %TEMP%\dotnet_diag<uid>.exe on Windows, chmods it 0755, and detached-spawns it via /bin/sh -c "<path> &" or cmd start /b. There is no signature or hash verification of the fetched bytes. A marker file at.analytics_state/analytics_state gates re-execution to roughly a 6-hour interval. A second parallel dropper implementation is shipped in lib/telemetry.js (assembles base64 chunks over DNS TXT, writes an 'extension' file, chmods 755, spawns /bin/sh). Hostname reassembly via.join(''), split-string obfuscation of DNS resolvers, and hidden filenames masquerading as OS cache/diagnostics files (.cache_, dotnet_diag_) indicate deliberate evasion rather than telemetry. On any require() of this package, arbitrary attacker-controlled native code executes on the installer's host.

Malicious versions

1 flagged

35.9.3

Indicators of compromise (SHA-256)

2629721fa3107222cef1f1669d474e7b3b45346ed87a455a168c1d199d9c6492

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-zod-wip-api (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-zod-wip-api across your stack and pipelines.
If you installed it — respond
devplatform-zod-wip-api establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If devplatform-zod-wip-api 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 devplatform-zod-wip-api 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. devplatform-zod-wip-api on npm has been identified as a malicious package (version 35.9.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015714

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-zod-wip-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database