@railone/image-utilsnpm
@railone/image-utils is a confirmed malicious npm package (MAL-2026-16261) that executes malicious code on install (malicious version 1.1.10). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @railone/image-utils (npm)
What this malware does
On import, index.js calls initialize() which spawns a detached, stdio-suppressed, windowsHide node loader.js child (init.js) and records its PID. loader.js HTTPS-fetches JSON from https://api.npoint.io/641d37178a880b1e8b8f, base64-decodes the code field, and executes it via new Function('require','__dirname','__filename','module','exports', decodedCode)(...), running arbitrary attacker-controlled JavaScript on the installer's host with full Node privileges and network access. The npoint.io endpoint is a mutable third-party JSON store whose contents can be changed at any time by whoever controls that resource, giving that party a persistent remote code-push channel into every installer. The package advertises itself as an image/runtime utility exposing getProcessInfo/getRuntimeInfo, but no such functions are exported; internal comments identify the code as an 'ID-10 Client Module' for 'device information collection and remote code execution' with 'AUTO-START ON IMPORT'.
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 @railone/image-utils (version 1.1.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @railone/image-utils across your stack and pipelines.
If you installed it — respond
Remove @railone/image-utils 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 @railone/image-utils 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 @railone/image-utils 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 @railone/image-utils-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.