hubert-verify-primary-email-amnpm
hubert-verify-primary-email-am is a confirmed malicious npm package (MAL-2026-12391) that executes malicious code on install (malicious version 20.4.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hubert-verify-primary-email-am (npm)
What this malware does
[email protected] presents itself as an email-verification library but on require of index.js loads init.js, which reconstructs remote hostnames from split string arrays (joining to oob-worker.cf103-070.workers.dev and subdomains of dl.well1.site) to evade static inspection. It selects a platform-specific asset, downloads bytes over HTTPS with a DNS-TXT-record chunked-fetch fallback (base64 chunks assembled from TXT records under c.<domain>), writes the binary to /var/tmp or %TEMP% under cover-story names such as.cache / dotnet_diag_, chmods it 0755, and detached-spawns it via spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) (or cmd on Windows). There is no hash or signature verification, the destinations are unrelated to the declared email-verification purpose, and the delivery hosts are attacker-mutable. Requiring the package yields arbitrary native code execution on the installer's machine under the installer's user account.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hubert-verify-primary-email-am (version 20.4.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hubert-verify-primary-email-am across your stack and pipelines.
If you installed it — respond
Remove hubert-verify-primary-email-am 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 hubert-verify-primary-email-am 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 hubert-verify-primary-email-am 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks hubert-verify-primary-email-am-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.