Which versions of dolyame-boxy-independent-bnpl-table are malicious?

The following npm versions of dolyame-boxy-independent-bnpl-table are flagged malicious: 35.3.4. Treat any of these as compromised.

How do I remediate dolyame-boxy-independent-bnpl-table if I installed it?

dolyame-boxy-independent-bnpl-table is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed dolyame-boxy-independent-bnpl-table — how do I know if it already compromised me?

If dolyame-boxy-independent-bnpl-table 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 dolyame-boxy-independent-bnpl-table part of a known attack campaign?

Yes — dolyame-boxy-independent-bnpl-table is associated with the IN-MAL-2026-015660 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 dolyame-boxy-independent-bnpl-table 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 dolyame-boxy-independent-bnpl-table (version 35.3.4). 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-table across your stack and pipelines.

Malicious package

dolyame-boxy-independent-bnpl-tablenpm

dolyame-boxy-independent-bnpl-table is a confirmed malicious npm package (MAL-2026-13331) that steals credentials and exfiltrates sensitive data (malicious version 35.3.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-independent-bnpl-table (npm)

MAL-2026-13331

Immediate action

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

npm uninstall dolyame-boxy-independent-bnpl-table

What this malware does

On require() of the package, index.js loads init.js which assembles obfuscated Cloudflare Workers hostnames (oob-worker.cf*.workers.dev) from string-split fragments joined at runtime, with a DNS-TXT-based fallback resolver using *.dl.wel1.ru domains. It downloads a platform-specific binary (/pkg/package, /pkg/package.exe, /pkg/loader_mac, /pkg/package-arm64) via https.get, writes the opaque payload to /var/tmp or the Windows TEMP directory under disguised names (.cache<hex> or dotnet_diag_<hex>.exe), chmods it to 0755, and spawns it detached via /bin/sh -c or cmd /c start. A stamp file at /tmp/.analytics_state rate-limits re-execution, and DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env vars are honored as a cover story framing this as an analytics SDK. A second module, lib/telemetry.js, is bundled in the same tarball with the same fetch-decode-write-chmod-spawn shape and additional API-name concatenation obfuscation (require('child_'+'process'), fs['chmod'+'Sync']). Package name and 'bnpl-table' framing do not match the observed behavior.

Malicious versions

1 flagged

35.3.4

Indicators of compromise (SHA-256)

fd3ad7593e26ae49876e0310a51ac122ddcb6878eefddc74a5828cce061d200b

Detection & response playbook

Credential / info stealer

Find 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-table (version 35.3.4). 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-table across your stack and pipelines.
If you installed it — respond
dolyame-boxy-independent-bnpl-table is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dolyame-boxy-independent-bnpl-table 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-table 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. dolyame-boxy-independent-bnpl-table on npm has been identified as a malicious package (version 35.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015660

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-independent-bnpl-table-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database