Which versions of @hibachi-xyz/types are malicious?

The following npm versions of @hibachi-xyz/types are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @hibachi-xyz/types if I installed it?

@hibachi-xyz/types 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 @hibachi-xyz/types — how do I know if it already compromised me?

If @hibachi-xyz/types was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @hibachi-xyz/types part of a known attack campaign?

Yes — @hibachi-xyz/types is associated with the IN-MAL-2026-010698 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 @hibachi-xyz/types across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @hibachi-xyz/types (version 99.0.0).

Malicious package

@hibachi-xyz/typesnpm

Advisory published Jul 16, 2026Updated Jul 17, 2026

@hibachi-xyz/types is a confirmed malicious npm package (MAL-2026-10715) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hibachi-xyz/types (npm)

MAL-2026-10715

Immediate action

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

npm uninstall @hibachi-xyz/types

What this malware does

The package presents itself as 'Type definitions' for the @hibachi-xyz scope at version 99.0.0, but index.js exports an empty object and its only behavior on module load is credential and host exfiltration. On require(), the code enumerates process.env and filters keys matching /KEY|SECRET|TOKEN|PASS|PRIV|SIGN|AWS|CIRCLE|GITHUB|DB|RDS|SENTRY|PYPI|NPM|DOCKER|KUBE|TUNNEL|CF_/i, captures os.hostname() and os.userInfo().username, and runs whoami && id && cat /proc/1/cgroup via child_process.execSync to fingerprint the host and detect container/CI context. The collected secrets and reconnaissance data are POSTed as JSON to https://jorijo.xyz:8443/t with TLS certificate verification disabled (rejectUnauthorized:false). The name/version shape (generic 'types' subpackage under an organization scope at an inflated version 99.0.0) is consistent with dependency-confusion or version-squat targeting the @hibachi-xyz org.

The OpenSSF Package Analysis project identified '@hibachi-xyz/types' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

214e1b690352ce0af70ce6a37d3b7ac4d8dec4269dc7606b7a65fbb6d4406e8b

51e71c95ff8fc1a03433cfc6ce2b1da6199175e11db673b35349bf852a6c5e5f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @hibachi-xyz/types (version 99.0.0).
If you installed it — respond
@hibachi-xyz/types 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 @hibachi-xyz/types was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @hibachi-xyz/types on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010698

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @hibachi-xyz/types-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