NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dolyame-ui-paginationnpm

Advisory published Updated

dolyame-ui-pagination is a confirmed malicious npm package (MAL-2026-13172) that executes malicious code on install (malicious version 35.2.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-pagination (npm)

MAL-2026-13172
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dolyame-ui-pagination

What this malware does

On require of the package, index.js loads./polyfill.js, which immediately executes a dropper routine. The dropper assembles destination hostnames at runtime via array-join string splitting to evade static matching, resolving to Cloudflare Workers endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev). A platform-specific binary is downloaded, written to /tmp or %TEMP% under disguised names such as.cache<hex> or dotnet_diag_<hex>.exe, chmod'd to 0755, and spawned detached via /bin/sh -c or cmd. A secondary covert channel resolves TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, base64-decoding the concatenated TXT fragments into an executable buffer when the HTTPS mirrors fail. A sibling module lib/telemetry.js ships the same dropper primitives (base64-decoded buffer, split-property fs['chmod'+'Sync'], /bin/sh spawn) though it is not on the entrypoint graph from index.js. Destinations are unrelated to the package's stated purpose (a UI pagination component), unpinned, and unverified; the fetched bytes are opaque and executed.

Malicious versions

1 flagged
35.2.5

Indicators of compromise (SHA-256)

7acc8dae4428c1b1cbf6ba1dc8199cdd4b07bf06aceca87a603fd34fd18834f7

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for dolyame-ui-pagination (version 35.2.5).

  2. If you installed it — respond

    Remove dolyame-ui-pagination from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If dolyame-ui-pagination was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-ui-pagination on npm has been identified as a malicious package (version 35.2.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015596

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-pagination-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.

Explore

dolyame-ui-pagination (npm) malicious package — MAL-2026-13172 | O3 Security