Which versions of tw-webkit-universal are malicious?

The following npm versions of tw-webkit-universal are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate tw-webkit-universal if I installed it?

Remove tw-webkit-universal from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed tw-webkit-universal — how do I know if it already compromised me?

If tw-webkit-universal 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 tw-webkit-universal part of a known attack campaign?

Yes — tw-webkit-universal is associated with the GHSA-w7cj-94c9-vxwj, RLMA-2025-05535, RLUA-2025-05972 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 tw-webkit-universal 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 tw-webkit-universal (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tw-webkit-universal across your stack and pipelines.

Malicious package

tw-webkit-universalnpm

tw-webkit-universal is a confirmed malicious npm package (MAL-2025-48288) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tw-webkit-universal (npm)

MAL-2025-48288

Immediate action

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

npm uninstall tw-webkit-universal

What this malware does

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.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

7fbf2c831086ca3205f21c4113b6b26c6a3a854dcf9b56b72683b10995a7fe43

00fa734c7dcae07d8ab3313b2dd7d2707e449d9f0bacecc501843e6b13d574f0

e12d7c73479092ab9c013277dddbf7d08ed0e0f171a9a441e85f0c507c8bf33a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tw-webkit-universal (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tw-webkit-universal across your stack and pipelines.
If you installed it — respond
Remove tw-webkit-universal from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tw-webkit-universal 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 tw-webkit-universal 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. tw-webkit-universal on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w7cj-94c9-vxwjRLMA-2025-05535RLUA-2025-05972

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks tw-webkit-universal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database