Which versions of @actbase/react-native-tiktok are malicious?

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

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

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

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

Yes — @actbase/react-native-tiktok is associated with the GHSA-47vw-pwr5-fvr4 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-native-tiktok 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-native-tiktok (version 1.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @actbase/react-native-tiktok across your stack and pipelines.

Malicious package

@actbase/react-native-tiktoknpm

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

MAL-2025-190712

Immediate action

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

npm uninstall @actbase/react-native-tiktok

What this malware does

The package @actbase/react-native-tiktok 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.1.3

Indicators of compromise (SHA-256)

91177de19c1dec6176ca433364e5e6a96637f899a71badcaf7e50f3de895d6a1

e30674f65fae1c8cebcf4d015086a943502402cc93f3559653c406c592a62366

52136f6075e835a431450b87003a8458c1922c4479b04390fdbc8e9ca009c85e

a38b2d65c8132e6a41a39a23474a9c2fc75bfca1b42e4a553138b38ea9553d09

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

Campaign

GHSA-47vw-pwr5-fvr4

References

Credits

Amazon Inspector · finder

Detect & block this

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