hubert-appointment-v2-task-create-amnpm
hubert-appointment-v2-task-create-am is a confirmed malicious npm package (MAL-2026-12066) that executes malicious code on install (malicious version 20.4.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hubert-appointment-v2-task-create-am (npm)
What this malware does
On require(), platform.js reconstructs destination hostnames from split-string arrays (e.g. 'oob-worker.cf103-070.workers.dev' assembled from ['oob-w','ork','er.cf103-070.','worker','s.','dev']) and downloads an unpinned platform-specific binary via https.get over a set of anonymous *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT base64 fallback resolved through *.dl.well1.site (e.g. 'tin.dl.well1.site' assembled from ['tin.dl.well1.','si','te']). The downloaded bytes are written to /var/tmp/.cache<tok> on Linux or to the Windows TEMP directory as dotnet_diag_<tok>.exe, chmodded 0755, and spawned detached via spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or cmd /c start. A 'telemetry/analytics' cover story with a DO_NOT_TRACK opt-out and an analytics_state cooldown marker is layered around the drop-and-exec. No hash or signature verification is performed on the fetched binary.
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-appointment-v2-task-create-am (version 20.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hubert-appointment-v2-task-create-am across your stack and pipelines.
If you installed it — respond
Remove hubert-appointment-v2-task-create-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-appointment-v2-task-create-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-appointment-v2-task-create-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-appointment-v2-task-create-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.