hubert-document-actual-insurance-rules-amnpm
hubert-document-actual-insurance-rules-am is a confirmed malicious npm package (MAL-2026-12390) that executes malicious code on install (malicious version 20.5.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hubert-document-actual-insurance-rules-am (npm)
What this malware does
On require of the package, index.js loads helpers.js which downloads a platform-specific executable from a rotating list of Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback under *.dl.well1.site. The hostnames are assembled at runtime by splitting and joining string fragments to hide them from static analysis. The fetched binary is written to a disguised path in /tmp or %TEMP% (e.g. dotnet_diag<hex>.exe or.cache_<hex>), chmodded 0o755 on POSIX, and spawned detached via /bin/sh -c or cmd. Cover-story identifiers such as analytics_state, DISABLE_TELEMETRY, and dotnet_diag_ frame the behavior as telemetry, but the actual code path is a fetch-and-execute dropper of attacker-controlled binaries that fires on module load.
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-document-actual-insurance-rules-am (version 20.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hubert-document-actual-insurance-rules-am across your stack and pipelines.
If you installed it — respond
Remove hubert-document-actual-insurance-rules-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-document-actual-insurance-rules-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-document-actual-insurance-rules-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-document-actual-insurance-rules-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.