Which versions of dolyame-boxy-atom-container are malicious?

The following npm versions of dolyame-boxy-atom-container are flagged malicious: 35.3.2. Treat any of these as compromised.

How do I remediate dolyame-boxy-atom-container if I installed it?

dolyame-boxy-atom-container 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 dolyame-boxy-atom-container — how do I know if it already compromised me?

If dolyame-boxy-atom-container 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-atom-container part of a known attack campaign?

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

Malicious package

dolyame-boxy-atom-containernpm

dolyame-boxy-atom-container is a confirmed malicious npm package (MAL-2026-13292) that opens a backdoor for remote access (malicious version 35.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-atom-container (npm)

MAL-2026-13292

Immediate action

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

npm uninstall dolyame-boxy-atom-container

What this malware does

On require() of the package, index.js loads helpers.js which invokes setup() at module load. setup() selects a platform-specific payload path (linux/darwin/win32), rotates through obfuscated Cloudflare Workers hostnames (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev), downloads bytes over HTTPS, writes them to /var/tmp/.cache<rnd> or %TEMP%/dotnet_diag_<rnd>.exe, sets mode 0755, and detaches execution via /bin/sh -c or cmd /c start. A DNS-TXT chunked fallback reassembles a base64 payload from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru when HTTPS fetch fails. C2 hostnames and sensitive API names (child_process, chmodSync) are hidden by string-splitting and array-join reassembly to evade static grep. A parallel dropper implementation lives in lib/telemetry.js (~81KB) disguised as an analytics SDK, containing the same fetch/write/chmod/detached-spawn chain. The package's declared purpose is reusable UI components; native-binary download and execution from anonymous Cloudflare Workers subdomains has no legitimate role in that scope, no publisher affiliation, and no hash or signature verification.

Malicious versions

1 flagged

35.3.2

Indicators of compromise (SHA-256)

8fb29bd9c1d233b882994262382b5f0b5b21cb2b868c139720d5ec9533ce9301

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

Campaign

IN-MAL-2026-015698

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-atom-container-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