Which versions of devplatform-cra-template are malicious?

The following npm versions of devplatform-cra-template are flagged malicious: 35.6.2. Treat any of these as compromised.

How do I remediate devplatform-cra-template if I installed it?

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

I already installed devplatform-cra-template — how do I know if it already compromised me?

If devplatform-cra-template 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-cra-template part of a known attack campaign?

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

Malicious package

devplatform-cra-templatenpm

devplatform-cra-template is a confirmed malicious npm package (MAL-2026-12706) that typosquats a legitimate package to trick installs (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-cra-template (npm)

MAL-2026-12706

Immediate action

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

npm uninstall devplatform-cra-template

What this malware does

On require('devplatform-cra-template'), index.js loads bootstrap.js, which selects a per-platform payload path and downloads bytes over HTTPS from one of three concatenation-obfuscated Cloudflare Workers mirrors (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT fallback resolving through sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under names mimicking legitimate tooling (.cache<hex>, dotnet_diag_<hex>.exe), chmod 755'd, and spawned detached via /bin/sh -c or cmd.exe. Every network destination, the child_process require, and chmodSync are assembled from split-string arrays joined at runtime to defeat static analysis. A second, structurally identical dropper is shipped in lib/telemetry.js (~81 KB, disguised as an analytics SDK): base64-assembled bytes, chmod 755, cp.spawn('/bin/sh', ['-c', filePath + ' &'],...); it is not reachable from index.js in this version but is present in the tarball. The package name resembles the legitimate cra-template family, consistent with a typosquat lure delivering remote code to any consumer that requires it.

Malicious versions

1 flagged

35.6.2

Indicators of compromise (SHA-256)

23e3df86e82704f0b114e616b4dc7f4acd0e5c377a336a61cb987625a31f3940

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

Campaign

IN-MAL-2026-015063

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-cra-template-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