Which versions of @actbase/react-daum-postcode are malicious?

The following npm versions of @actbase/react-daum-postcode are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate @actbase/react-daum-postcode if I installed it?

@actbase/react-daum-postcode 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 @actbase/react-daum-postcode — how do I know if it already compromised me?

If @actbase/react-daum-postcode 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 @actbase/react-daum-postcode part of a known attack campaign?

Yes — @actbase/react-daum-postcode is associated with the GHSA-h89h-8r6f-cvr4 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 @actbase/react-daum-postcode 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 @actbase/react-daum-postcode (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @actbase/react-daum-postcode across your stack and pipelines.

Malicious package

@actbase/react-daum-postcodenpm

Malicious code in @actbase/react-daum-postcode (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190708

Immediate action

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

npm uninstall @actbase/react-daum-postcode

What this malware does

The package @actbase/react-daum-postcode 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.5

Indicators of compromise (SHA-256)

50ebc3357b616bd8435bcb7150166fb8f6117e9ca75ea50570eebb1d6d4b850c

3b6730961ddc6bcfd14bc8564e2a8ef3d34d757e1ffae65ed7ff88232e115104

ba66ef976090cbfdefaa380db31b7de3eed06cc4527ed838883314e3383d5418

10694a0b423d34f89681244c4b0e2027b89686881fb3866efbaa5b5fa0f4d159

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

Campaign

GHSA-h89h-8r6f-cvr4

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @actbase/react-daum-postcode-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