Which versions of beaver-ui-pagination are malicious?

The following npm versions of beaver-ui-pagination are flagged malicious: 35.3.7. Treat any of these as compromised.

How do I remediate beaver-ui-pagination if I installed it?

Remove beaver-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.

I already installed beaver-ui-pagination — how do I know if it already compromised me?

If beaver-ui-pagination 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 beaver-ui-pagination part of a known attack campaign?

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

Malicious package

beaver-ui-paginationnpm

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

Malicious code in beaver-ui-pagination (npm)

MAL-2026-12820

Immediate action

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

npm uninstall beaver-ui-pagination

What this malware does

On require('beaver-ui-pagination'), index.js loads init.js which selects a platform key and downloads a binary from string-split-obfuscated hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT chunked-base64 fallback via *.dl.wel1.ru subdomains. The fetched binary is written to /var/tmp or %TEMP% under a disguised name (.cache<rnd> on POSIX, dotnet_diag_<rnd>.exe on Windows), chmod 0755 on POSIX, and spawned detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled at runtime from array.join to evade static inspection, and env-var opt-outs (DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK) plus an 'analytics_state' marker file frame the behavior as telemetry despite the fetch-and-execute flow. A sibling lib/telemetry.js not currently reachable from index.js ships a second copy of the dropper primitives (dynamic require('child_'+'process'), base64-chunked buffer, chmodSync 0755, /bin/sh spawn of a filePath).

Malicious versions

1 flagged

35.3.7

Indicators of compromise (SHA-256)

2db8f562892f21caf2a12230c52507a333a5ada223f98964094838657072adcb

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-pagination (version 35.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging beaver-ui-pagination across your stack and pipelines.
If you installed it — respond
Remove beaver-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.
Did it already run?
If beaver-ui-pagination 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 beaver-ui-pagination 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. beaver-ui-pagination on npm has been identified as a malicious package (version 35.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015559

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks beaver-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database