Which versions of pdf-to-office are malicious?

The following npm versions of pdf-to-office are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.1.2. Treat any of these as compromised.

How do I remediate pdf-to-office if I installed it?

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

If pdf-to-office was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is pdf-to-office part of a known attack campaign?

Yes — pdf-to-office is associated with the RLMA-2025-02361, RLUA-2025-06445 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 pdf-to-office across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pdf-to-office (4 malicious versions).

Malicious package

pdf-to-officenpm

Advisory published Apr 23, 2025Updated Dec 24, 2025

pdf-to-office is a confirmed malicious npm package (MAL-2025-3412) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pdf-to-office (npm)

MAL-2025-3412

Immediate action

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

npm uninstall pdf-to-office

Malicious versions

4 flagged

1.0.01.0.11.0.21.1.2

Indicators of compromise (SHA-256)

e870b5a49d0b302ec9051e932a4dd660501e85db187672ec7e7b7fb58129212f

af6e2212a04fc9764cbe863176d0ab0f5a1964518ae66fc9572a997e8376252c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pdf-to-office (4 malicious versions).
If you installed it — respond
Remove pdf-to-office 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 pdf-to-office was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. pdf-to-office on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02361RLUA-2025-06445

References

reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks pdf-to-office-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