Malicious code in beaver-ui-popover-card (npm)
The npm package 'beaver-ui-popover-card' version 35.4.4 contains malicious code that downloads and executes platform-specific binaries from obfuscated Cloudflare Workers endpoints and fallback DNS TXT resolvers. The binaries are saved under disguised filenames, given executable permissions, and run detached without signature or hash verification. The package also includes a secondary dropper disguised as a telemetry SDK using obfuscation techniques. This behavior occurs immediately upon requiring the package, indicating clear dropper activity.
AI Analysis
Technical Summary
The 'beaver-ui-popover-card' npm package version 35.4.4 includes malicious functionality in its _support.js and lib/telemetry.js files. Upon require(), it downloads platform-specific binaries from dynamically assembled Cloudflare Workers hostnames with DNS TXT fallback resolvers unrelated to the package publisher. The binaries are saved under disguised names, made executable, and executed detached via shell commands without any integrity verification. Additionally, a second dropper embedded in telemetry.js uses runtime string concatenation and base64 decoding to hide its operations. Hostname obfuscation, covert DNS fallback, disguised filenames, and detached execution collectively confirm this package acts as a dropper malware.
Potential Impact
This malicious package can execute arbitrary platform-specific binaries on the host system without user consent or verification, potentially leading to full system compromise or further malware deployment. The lack of signature or hash verification and the use of obfuscation techniques increase the risk of undetected execution. Any project that includes this package version risks executing untrusted code, which can lead to data theft, system disruption, or persistence of malicious payloads.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately remove version 35.4.4 of 'beaver-ui-popover-card' from their projects and avoid using this package version. Consider auditing dependencies for this package and replacing it with a trusted alternative. Monitor for updates or advisories from the package publisher or security vendors for further remediation guidance. Since this is a malicious package, no legitimate fix is expected; removal and avoidance are the primary mitigations.
Malicious code in beaver-ui-popover-card (npm)
Description
The npm package 'beaver-ui-popover-card' version 35.4.4 contains malicious code that downloads and executes platform-specific binaries from obfuscated Cloudflare Workers endpoints and fallback DNS TXT resolvers. The binaries are saved under disguised filenames, given executable permissions, and run detached without signature or hash verification. The package also includes a secondary dropper disguised as a telemetry SDK using obfuscation techniques. This behavior occurs immediately upon requiring the package, indicating clear dropper activity.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'beaver-ui-popover-card' npm package version 35.4.4 includes malicious functionality in its _support.js and lib/telemetry.js files. Upon require(), it downloads platform-specific binaries from dynamically assembled Cloudflare Workers hostnames with DNS TXT fallback resolvers unrelated to the package publisher. The binaries are saved under disguised names, made executable, and executed detached via shell commands without any integrity verification. Additionally, a second dropper embedded in telemetry.js uses runtime string concatenation and base64 decoding to hide its operations. Hostname obfuscation, covert DNS fallback, disguised filenames, and detached execution collectively confirm this package acts as a dropper malware.
Potential Impact
This malicious package can execute arbitrary platform-specific binaries on the host system without user consent or verification, potentially leading to full system compromise or further malware deployment. The lack of signature or hash verification and the use of obfuscation techniques increase the risk of undetected execution. Any project that includes this package version risks executing untrusted code, which can lead to data theft, system disruption, or persistence of malicious payloads.
Defensive Guidance
No official patch or remediation is currently documented. Users should immediately remove version 35.4.4 of 'beaver-ui-popover-card' from their projects and avoid using this package version. Consider auditing dependencies for this package and replacing it with a trusted alternative. Monitor for updates or advisories from the package publisher or security vendors for further remediation guidance. Since this is a malicious package, no legitimate fix is expected; removal and avoidance are the primary mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12821
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a738536bf8831d5394f0be7
Added to database: 08/05/2026, 18:47:18 UTC
Last enriched: 08/05/2026, 18:58:54 UTC
Last updated: 08/05/2026, 23:35:47 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.