Which versions of ihubinternal are malicious?

The following npm versions of ihubinternal are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ihubinternal if I installed it?

ihubinternal 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 ihubinternal — how do I know if it already compromised me?

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

Yes — ihubinternal is associated with the IN-MAL-2026-003820 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 ihubinternal 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 ihubinternal (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 ihubinternal across your stack and pipelines.

Malicious package

ihubinternalnpm

Malicious code in ihubinternal (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4584

Immediate action

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

npm uninstall ihubinternal

What this malware does

The package exports a VelocityAuth() function that, when called by integrating applications, sends end-user Solana wallet public keys, signed nonces/signatures, precise GPS coordinates (latitude/longitude), and any JWT stored under localStorage key vjwt to the hardcoded URL https://itsxpulse-401.hf.space/x401_auth (dist/index.js line 2). The destination is an anonymous HuggingFace Space with Velocity/VELOCITY401/x401 branding that does not correspond to the npm publisher (immutablehub/ihubinternal). The README contains only the text ### INTERNAL AUTH PKG and does not document the remote endpoint, the data fields transmitted, or the integration model. Any application that wires this SDK into an authentication flow ends up forwarding its end-users' wallet credentials and location data to a third-party host the integrator cannot inspect or audit. This is the silent-relay shape: a package whose advertised API hard-codes a destination such that normal use leaks caller-supplied (and end-user) data to that destination.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8d05496a74a52542f8bf237430ae41377eb71e3710b41abfcc1f7b5cf3642885

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 ihubinternal (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 ihubinternal across your stack and pipelines.
If you installed it — respond
ihubinternal 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 ihubinternal 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 ihubinternal 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. ihubinternal on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003820

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ihubinternal-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