dolyame-boxy-independent-bnpl-partnersnpm
dolyame-boxy-independent-bnpl-partners is a confirmed malicious npm package (MAL-2026-13324) that typosquats a legitimate package to trick installs (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-independent-bnpl-partners (npm)
What this malware does
On require of the package, index.js loads platform.js, which assembles attacker-controlled hostnames via array-split-and-join obfuscation (oob-worker.*.workers.dev variants and sdk/ext/pkg/net.dl.wel1.ru), fetches a platform-specific binary over HTTPS with a DNS-TXT base64 fallback channel, writes it to /var/tmp or %TEMP% under disguised names such as.cache<hex> or dotnet_diag_<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. Cover-story identifiers such as analytics_state and a DISABLE_TELEMETRY opt-out are used to frame the behavior as telemetry. The package name impersonates a Russian BNPL partner integration, and none of the shipped code implements that stated purpose.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-independent-bnpl-partners (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 dolyame-boxy-independent-bnpl-partners across your stack and pipelines.
If you installed it — respond
dolyame-boxy-independent-bnpl-partners is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-boxy-independent-bnpl-partners, 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 dolyame-boxy-independent-bnpl-partners 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 dolyame-boxy-independent-bnpl-partners 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-boxy-independent-bnpl-partners-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.