Which versions of smart-parser are malicious?

The following npm versions of smart-parser are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate smart-parser if I installed it?

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

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

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

Malicious package

smart-parsernpm

Malicious code in smart-parser (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192863

Immediate action

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

npm uninstall smart-parser

What this malware does

The package smart-parser was found to contain malicious code.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

9fb1aedcf7d6d1808bb71d299c97fb963e3674571d133ed6cfccd846a861066f

077a3aaa416c1f13b15911f6c7b8569859f046edbaeb64242bc8ecd5e32c75bb

e9ef2bb631a949db16606844323b2a34a6e4bb409dec8ee03aac8ba1020de920

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

Campaign

RLMA-2025-06483RLUA-2026-01578

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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