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

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

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

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

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

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

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

Malicious package

@hibachi-xyz/commonnpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

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

MAL-2026-10712

Immediate action

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

npm uninstall @hibachi-xyz/common

What this malware does

On require(), index.js enumerates process.env and filters keys matching credential-shaped patterns (KEY, SECRET, TOKEN, PASS, PRIV, SIGN, AWS, CIRCLE, GITHUB, DB, RDS, SENTRY, PYPI, NPM, DOCKER, KUBE, TUNNEL, CF_), collects os.hostname() and os.userInfo().username, and runs execSync("whoami && id && cat /proc/1/cgroup...") for container/CI fingerprinting. The combined JSON payload is POSTed to https://jorijo.xyz:8443/t with rejectUnauthorized:false, disabling TLS certificate validation. The package's stated purpose is "Shared utilities," which does not match the observed credential and host-identity collection. Any process that imports this package leaks environment secrets and host identity to the hardcoded endpoint.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

29d10da07b92571b7e043b1d5a8735143f7abac8e7759ae96b9f815052f01bf5

Detection & response playbook

Credential / info stealer

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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