Which versions of stellarfix are malicious?

The following npm versions of stellarfix are flagged malicious: 1.0.0, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate stellarfix if I installed it?

stellarfix is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed stellarfix — how do I know if it already compromised me?

If stellarfix 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 stellarfix part of a known attack campaign?

Yes — stellarfix is associated with the IN-MAL-2026-014472, IN-MAL-2026-015809, IN-MAL-2026-015810 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 stellarfix 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 stellarfix (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stellarfix across your stack and pipelines.

Malicious package

stellarfixnpm

stellarfix is a confirmed malicious npm package (MAL-2026-12216) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.3, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stellarfix (npm)

MAL-2026-12216

Immediate action

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

npm uninstall stellarfix

What this malware does

stellarfix ships a.NET Windows executable at bin/stellarfn.exe and a postinstall.js that enumerates bin/*.exe and unconditionally launches the first one via execFileSync during npm install. The package.json declares scripts.postinstall=node postinstall.js, so the binary runs automatically on any Windows installer. The bundled binary contains class and P/Invoke symbols consistent with a full remote-access trojan: a ClientSocket/ConnectServer C2 channel with AES-encrypted traffic, an XLogger module using SetWindowsHookEx / LowLevelKeyboardProc / WM_KEYDOWN / ToUnicodeEx to capture keystrokes and GetForegroundWindow / GetActiveWindowTitle to capture focused-window context, a SendBot/ChatID exfiltration pipeline, ProcessCritical (SetCurrentProcessIsCritical) anti-termination, an Uninstaller routine, a USBSpread module (USBThread/USBStart/USBCode) for removable-media propagation, a Plugin loader, and OpenUrl/ReportWindow/Monitoring command handlers. The package contains no legitimate library code; its sole install-time effect is delivering and running this binary on the installer's host.

Malicious versions

3 flagged

1.0.01.0.31.0.4

Indicators of compromise (SHA-256)

304faa7930c5efaa4ff655a7ce779e977ce5b6b59c4c15154fc96c82fead9d16

1e30554b98d24d905f55de80fb216bba2367d2259bdd251636eab19c8b19019a

aa63d1cc5db1027ec89a76a75db2e765cc0c951ca8b5324ac4ec9ef3e849d325

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stellarfix (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stellarfix across your stack and pipelines.
If you installed it — respond
stellarfix is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If stellarfix 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 stellarfix 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. stellarfix on npm has been identified as a malicious package (versions 1.0.0, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014472IN-MAL-2026-015809IN-MAL-2026-015810

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks stellarfix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database