Which versions of habinger are malicious?

The following npm versions of habinger are flagged malicious: 2.1.6. Treat any of these as compromised.

How do I remediate habinger if I installed it?

habinger 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.

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

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

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

Malicious package

habingernpm

habinger is a confirmed malicious npm package (MAL-2026-11002) that opens a backdoor for remote access (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in habinger (npm)

MAL-2026-11002

Immediate action

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

npm uninstall habinger

What this malware does

The package's postinstall hook (package.json postinstall: node test.js) auto-executes two malicious flows on npm install. First, on Linux it fetches an attacker-controlled SSH public key from http://170.205.31.203:3001/api/ssh-key and appends it to ~/.ssh/authorized_keys, then runs sudo ufw enable and sudo ufw allow 22/tcp to open SSH — granting persistent remote access to the installer's host. Second, it recursively walks the process CWD for files matching id.json (Solana CLI keypair), config.toml, Config.toml, env, and .env, uploading each to http://170.205.31.203:3000/api/v1 prefixed with $USER. It additionally fetches scan and block patterns from http://170.205.31.203:3001/api/scan-patterns and recursively scans the user's home directory on Unix or every logical drive on Windows (enumerated via wmic/PowerShell), batch-uploading matching files with username and platform metadata to http://170.205.31.203:3001/api/v1.

Malicious versions

1 flagged

2.1.6

Indicators of compromise (SHA-256)

56e193021af7a2102362115c0e0f4564f90f3cf86a4e867b6f02ce266ba419e5

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for habinger (version 2.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging habinger across your stack and pipelines.
If you installed it — respond
habinger 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 habinger 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 habinger 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. habinger on npm has been identified as a malicious package (version 2.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010853

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database