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

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

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

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

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

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

Malicious package

@actbase/react-native-simple-videonpm

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

MAL-2025-190796

Immediate action

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

npm uninstall @actbase/react-native-simple-video

What this malware does

The package @actbase/react-native-simple-video 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.13

Indicators of compromise (SHA-256)

0127d5ad05d2406fdedfb69d858031c730e9fb41a0fe99f6cffcc138863b2319

df9f78c8d60111302902eadd3b683dc87591b36eedaa9ecb63d445745091aee6

b23540ab05a7ec910cd399e9ceffa0a0ae6e78a87aa93681ac5c81d4f5a8821b

d5c2b9a0285fb1f8af8c912d8bc6aa0dcb8979cedb024ab617db8f8cfd7a7cdc

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

Campaign

GHSA-qrm3-qmp2-c48g

References

Credits

Amazon Inspector · finder

Detect & block this

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