Which versions of @actbase/css-to-react-native-transform are malicious?

The following npm versions of @actbase/css-to-react-native-transform are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate @actbase/css-to-react-native-transform if I installed it?

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

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

Yes — @actbase/css-to-react-native-transform is associated with the GHSA-9qhm-9r8j-hrhc 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/css-to-react-native-transform 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/css-to-react-native-transform (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @actbase/css-to-react-native-transform across your stack and pipelines.

Malicious package

@actbase/css-to-react-native-transformnpm

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

MAL-2025-190706

Immediate action

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

npm uninstall @actbase/css-to-react-native-transform

What this malware does

The package @actbase/css-to-react-native-transform 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.3

Indicators of compromise (SHA-256)

59794b962952c25c07e0cded6beb31d93497ac7edc4edab2f7f8b3fa91fe2d17

19bb30e7704436db9e7ac671839931de450cdcde7408b8c151337c6958433836

2fc8036b76be134bdb94abc326eac4a2ab762cc892b5682dddf194b7532ea566

cf6af7c8d4f8b19699bb79a45b6694deb36b19a45d9b083bccf7fc729b86aa96

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

Campaign

GHSA-9qhm-9r8j-hrhc

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @actbase/css-to-react-native-transform-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