Which versions of xmlwtf3 are malicious?

Every published version of xmlwtf3 on npm is considered malicious. Remove the package entirely.

How do I remediate xmlwtf3 if I installed it?

Remove xmlwtf3 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 xmlwtf3 — how do I know if it already compromised me?

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

Yes — xmlwtf3 is associated with the GHSA-qjqf-48qf-vvmr 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 xmlwtf3 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 xmlwtf3 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xmlwtf3 across your stack and pipelines.

Malicious package

xmlwtf3npm

Malicious code in xmlwtf3 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192673

Immediate action

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

npm uninstall xmlwtf3

What this malware does

The package xmlwtf3 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

f1aef41363b46dac1d30ba3bd916904df95fce8278f6b3abed14f7b48002d2c8

fdc397291400d5d396c50c42966b6c482fb92a577a17ad2440c2ab4c7f0619e6

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

Campaign

GHSA-qjqf-48qf-vvmr

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks xmlwtf3-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