Which versions of korea-administrative-area-geo-json-util are malicious?

The following npm versions of korea-administrative-area-geo-json-util are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate korea-administrative-area-geo-json-util if I installed it?

korea-administrative-area-geo-json-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 korea-administrative-area-geo-json-util — how do I know if it already compromised me?

If korea-administrative-area-geo-json-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 korea-administrative-area-geo-json-util part of a known attack campaign?

Yes — korea-administrative-area-geo-json-util is associated with the GHSA-hcg2-q4w7-7rff 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 korea-administrative-area-geo-json-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 korea-administrative-area-geo-json-util (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging korea-administrative-area-geo-json-util across your stack and pipelines.

Malicious package

korea-administrative-area-geo-json-utilnpm

Malicious code in korea-administrative-area-geo-json-util (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190774

Immediate action

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

npm uninstall korea-administrative-area-geo-json-util

What this malware does

The package korea-administrative-area-geo-json-util was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

49a0d8104edb1e0099ae24b328806fd32d0ec580ef6aa28dab0de975e4d48123

d3e5fc5ac9320c5c6de500011362abf25bbbebf4427f272bef9a58fa0d5c0f03

3f7d693ee1296f9423f2d6d3f3c0973a2cb61640f8eff5c671cf9d1021ad5be4

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 korea-administrative-area-geo-json-util (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging korea-administrative-area-geo-json-util across your stack and pipelines.
If you installed it — respond
korea-administrative-area-geo-json-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 korea-administrative-area-geo-json-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 korea-administrative-area-geo-json-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. korea-administrative-area-geo-json-util on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hcg2-q4w7-7rff

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks korea-administrative-area-geo-json-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