model-poc-suhailnpm
model-poc-suhail is a confirmed malicious npm package (MAL-2026-3030) that opens a backdoor for remote access (malicious versions 1.0.4, 1.0.5, 1.0.9…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in model-poc-suhail (npm)
What this malware does
Package ships poc.js which requires child_process and spawns /bin/sh, connecting its stdin/stdout to a TCP socket at 0.tcp.in.ngrok.io:10023. This gives whoever controls that ngrok tunnel an unauthenticated interactive shell on the installer's host. Execution is triggered automatically by the package.json postinstall lifecycle hook ("postinstall": "node poc.js"), so the reverse shell fires on every npm install.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
The OpenSSF Package Analysis project identified 'model-poc-suhail' @ 1.0.14 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for model-poc-suhail (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging model-poc-suhail across your stack and pipelines.
If you installed it — respond
model-poc-suhail establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If model-poc-suhail 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 model-poc-suhail 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks model-poc-suhail-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.