Which versions of json-to-table-util are malicious?

The following npm versions of json-to-table-util are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate json-to-table-util if I installed it?

json-to-table-util 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 json-to-table-util — how do I know if it already compromised me?

If json-to-table-util 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 json-to-table-util part of a known attack campaign?

Yes — json-to-table-util is associated with the IN-MAL-2026-011011 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 json-to-table-util 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 json-to-table-util (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 json-to-table-util across your stack and pipelines.

Malicious package

json-to-table-utilnpm

json-to-table-util is a confirmed malicious npm package (MAL-2026-11119) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in json-to-table-util (npm)

MAL-2026-11119

Immediate action

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

npm uninstall json-to-table-util

What this malware does

postinstall.js runs automatically on npm install and executes a shell pipeline via child_process.exec that collects hostname, user, working directory, uname, container/cgroup indicators, process tree, network info (/etc/resolv.conf, IPs), GitHub Actions CI variables (GITHUB_REPOSITORY, GITHUB_ACTOR, GITHUB_RUN_ID, RUNNER_NAME), and the entire process environment via env (filtering only npm_* noise). It also probes AWS IMDS at 169.254.169.254 and Tencent Cloud metadata at metadata.tencentyun.com to fingerprint cloud infrastructure. The aggregated output is base64-encoded and sent over plain HTTP via curl GET to the hardcoded Burp Collaborator subdomain pzs5w7ntzhsnepwk564lyfdci3oucl0a.oastify.com/z?d=<base64>. On CI runners this captures any secrets exported to the environment (cloud keys, GITHUB_TOKEN, tokens injected into the job).

The OpenSSF Package Analysis project identified 'json-to-table-util' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

63ee08885a126855fbc96dbbb6f8c4ef903d9dc8f2cb02fe0fa178a7db1ed904

2317bf7f973ca611fdd2215509ae94c302f868ae9fb5c5f00de0b6bd13fe3bc4

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 json-to-table-util (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 json-to-table-util across your stack and pipelines.
If you installed it — respond
json-to-table-util 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 json-to-table-util 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 json-to-table-util 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. json-to-table-util 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-011011

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks json-to-table-util-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