Which versions of revit-to-ifc-scheduler are malicious?

The following npm versions of revit-to-ifc-scheduler are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate revit-to-ifc-scheduler if I installed it?

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

If revit-to-ifc-scheduler 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 revit-to-ifc-scheduler part of a known attack campaign?

Yes — revit-to-ifc-scheduler is associated with the RLMA-2025-05937 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 revit-to-ifc-scheduler across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for revit-to-ifc-scheduler (version 1.0.1).

Malicious package

revit-to-ifc-schedulernpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

revit-to-ifc-scheduler is a confirmed malicious npm package (MAL-2025-191585) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in revit-to-ifc-scheduler (npm)

MAL-2025-191585

Immediate action

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

npm uninstall revit-to-ifc-scheduler

What this malware does

The package revit-to-ifc-scheduler was found to contain malicious code.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

13642224a5122f258429cf12ec0b7cf834710c726cd630678cdf32af058f3dbf

a27f38ca3d7137e9a86fceda4b0315a4cd618118bcbcbc1b17aec59d089d66e7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for revit-to-ifc-scheduler (version 1.0.1).
If you installed it — respond
Remove revit-to-ifc-scheduler 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 revit-to-ifc-scheduler 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. revit-to-ifc-scheduler on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05937

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks revit-to-ifc-scheduler-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