Which versions of @actbase/react-kakaosdk are malicious?

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

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

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

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

Yes — @actbase/react-kakaosdk is associated with the GHSA-mg32-pcj3-6rm8 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-kakaosdk 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-kakaosdk (version 0.9.27). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @actbase/react-kakaosdk across your stack and pipelines.

Malicious package

@actbase/react-kakaosdknpm

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

MAL-2025-190791

Immediate action

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

npm uninstall @actbase/react-kakaosdk

What this malware does

The package @actbase/react-kakaosdk 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

0.9.27

Indicators of compromise (SHA-256)

e9c4b509509bfbc3528248a0d08c1dd38e856e35750e58631db23271adf1f7b8

a48797e2088e681febf91726aa184436bf3fa96104d23f438a11b19f75ef0516

d37921a49882952de0b9dfac5aecd4d549b4f3171185e9ca7e03357c0305f089

826953e5a7eb8709525f0357016f81a70d87b54190bf4e18af0c970be6c53c04

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

Campaign

GHSA-mg32-pcj3-6rm8

References

Credits

Amazon Inspector · finder

Detect & block this

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