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

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

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

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

If @hibachi-xyz/config 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/config part of a known attack campaign?

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

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

Malicious package

@hibachi-xyz/confignpm

Advisory published Jul 16, 2026Updated Jul 17, 2026

@hibachi-xyz/config is a confirmed malicious npm package (MAL-2026-10713) 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/config (npm)

MAL-2026-10713

Immediate action

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

npm uninstall @hibachi-xyz/config

What this malware does

On require of the package's main entry, top-level code enumerates process.env and collects values whose keys match a credential-shaped regex (KEY, SECRET, TOKEN, PASS, PRIV, SIGN, AWS, CIRCLE, GITHUB, DB, RDS, SENTRY, PYPI, NPM, DOCKER, KUBE, TUNNEL, CF_). It also invokes child_process.execSync to run whoami && id && cat /proc/1/cgroup and collects hostname and username. The combined JSON payload is POSTed to https://jorijo.xyz:8443/t with TLS certificate verification disabled (rejectUnauthorized:false). The 99.0.0 version number under the @hibachi-xyz scope is consistent with a version-inflation typosquat or scope hijack of legitimate hibachi packages.

The OpenSSF Package Analysis project identified '@hibachi-xyz/config' @ 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)

2012c3b3a43f28209edf1c4b6fdbb0477c7c31f7574e37293cf7dd324f7f1e2f

4b4af2f9414079b2062bec53821ecf7f67924011261a4f0430450b8415e9b07e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @hibachi-xyz/config (version 99.0.0).
If you installed it — respond
@hibachi-xyz/config 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/config 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/config 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-010703

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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