# MAL-2026-13288: Malicious code in dolyame-boxy-atom-bnpl-info-card (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-atom-bnpl-info-card` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-w5cf-r9p7-fv9c

## What is MAL-2026-13288?

MAL-2026-13288 is a malicious package in dolyame-boxy-atom-bnpl-info-card, published on 5 Aug 2026. 

### Official description

On load, index.js requires./_loader.js which reconstructs anonymous host names via array-join obfuscation (['oob-worker.cf100-416.work','ers.','dev'].join('') and ['sdk.dl.wel','1.','ru'].join('')), selects a platform-specific payload path, downloads an opaque binary from those hosts with a DNS-TXT fallback via *.dl.wel1.ru, writes it to /var/tmp/.cache_<hex> on Unix or TEMP\dotnet_diag_<hex>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd. A marker file gates re-runs and env-var checks provide a cover-story opt-out. lib/telemetry.js repeats the same shape using string-concatenation obfuscation for require('child_'+'process') and fs['chmod'+'Sync']. No hash or signature verification is performed; the destinations are anonymous, mutable CDN hosts unrelated to any declared purpose. Filename shape (dolyame-boxy-atom-bnpl-info-card) is also consistent with a lookalike/lure name.

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.

## What should I do about MAL-2026-13288?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13288 is a malicious package: dolyame-boxy-atom-bnpl-info-card (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13288/ (Markdown: https://insights.sbomify.com/MAL-2026-13288/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13288

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13288/
Summaries are generated and may contain mistakes; the official description above is the record.