Which versions of abcotv-xml-parser are malicious?

The following npm versions of abcotv-xml-parser are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate abcotv-xml-parser if I installed it?

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

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

Yes — abcotv-xml-parser is associated with the RLMA-2024-00293, RLUA-2024-06100, RLUA-2026-10675 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 abcotv-xml-parser 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 abcotv-xml-parser (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abcotv-xml-parser across your stack and pipelines.

Malicious package

abcotv-xml-parsernpm

abcotv-xml-parser is a confirmed malicious npm package (MAL-2024-1713) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abcotv-xml-parser (npm)

MAL-2024-1713

Immediate action

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

npm uninstall abcotv-xml-parser

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4f793ae946cd0f90adbfbdac61aa76c646c1f10ee19389d8f952ebbef5914bb5

791f2571c1c819e22dd747fa9ac160169d9379022b7aef602432e40612dc46be

15f22d84b9b694c0ad3ee19aa6d8b23191fb5f5077bc3948930dbac6dd02a459

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

Campaign

RLMA-2024-00293RLUA-2024-06100RLUA-2026-10675

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks abcotv-xml-parser-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