Which versions of docflow-cryptopro are malicious?

The following npm versions of docflow-cryptopro are flagged malicious: 35.1.6. Treat any of these as compromised.

How do I remediate docflow-cryptopro if I installed it?

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

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

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

Malicious package

docflow-cryptopronpm

docflow-cryptopro is a confirmed malicious npm package (MAL-2026-13279) that executes malicious code on install (malicious version 35.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in docflow-cryptopro (npm)

MAL-2026-13279

Immediate action

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

npm uninstall docflow-cryptopro

What this malware does

On require of the package's main, platform.js downloads an opaque platform-specific binary from obfuscated Cloudflare Workers subdomains (hostnames assembled from split string fragments such as ['oob-worke','r.cf102-baf.workers','.d','ev']) with a DNS-TXT covert-channel fallback that reassembles a base64 payload from numbered TXT records under c.*.dl.wel1.ru. The binary is written to a temp path under a decoy name (e.g. dotnet_diag.exe,.cache_), chmod +x is applied on POSIX, and it is spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. Execution is gated by an 'analytics_state' marker and opt-out env-var checks that function as cover for the drop. The advertised purpose is 'cryptographic primitives', which does not match downloading and executing an unverified native binary from workers.dev hosts. The package name (docflow-cryptopro) resembles the CryptoPro / КриптоПро brand family and is not affiliated with that vendor.

Malicious versions

1 flagged

35.1.6

Indicators of compromise (SHA-256)

b838ab488feb43fe2b50d6cd00579d3c1528877ea84d935ca89d8d863528bd25

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

Campaign

IN-MAL-2026-015713

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks docflow-cryptopro-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