Skip to main content
MalwarePublished

dolyame-boxy-independent-bnpl-cards (npm) · Malicious Code

Affects dolyame-boxy-independent-bnpl-cardsSource GCVE Database

0

Malicious package : remove dolyame-boxy-independent-bnpl-cards and rotate any secrets on hosts that installed it.

Data as of 6 Aug 2026, 18:24 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13314

What to do

Remove dolyame-boxy-independent-bnpl-cards from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
npmdolyame-boxy-independent-bnpl-cardsAffected
  • =35.7.6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5b2211179bcef10cb641d7ad848be2a71a3048d90108c4651b471ba60404f2d2) On import, index.js requires setup.js, which downloads an opaque binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS TXT covert-channel fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The payload is written to /tmp or %TEMP% under a disguised name (dotnet_diag_<uid>.exe on Windows,.cache_<uid> on Unix), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. There is no hash or signature verification, hostnames are assembled from array fragments joined at runtime, and the download destinations are unrelated to the package's stated BNPL-cards purpose. A lockfile named.analytics_state and opt-out env vars named DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK are used as a telemetry cover story. ## Source: ghsa-malware (52dea7d898c8f1e0fa0c6af08e0ada75adc49dfbfc69a89ba5068f4bd9a7b5af) 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.

References

Community reviews

Loading reviews…