Which versions of financialtimes-classic are malicious?

The following npm versions of financialtimes-classic are flagged malicious: 1.0.1, 1.1.0, 1.2.0. Treat any of these as compromised.

How do I remediate financialtimes-classic if I installed it?

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

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

Yes — financialtimes-classic is associated with the RLMA-2024-01024, RLUA-2024-06584, RLUA-2025-06353 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 financialtimes-classic across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for financialtimes-classic (3 malicious versions).

Malicious package

financialtimes-classicnpm

Advisory published Jun 25, 2024Updated Dec 24, 2025

financialtimes-classic is a confirmed malicious npm package (MAL-2024-2370) that executes malicious code on install (malicious versions 1.0.1, 1.1.0, 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in financialtimes-classic (npm)

MAL-2024-2370

Immediate action

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

npm uninstall financialtimes-classic

Malicious versions

3 flagged

1.0.11.1.01.2.0

Indicators of compromise (SHA-256)

dceb6a668818328d7e60d3cf76314b98fab890e2b3ae63b505049136eacd3883

2bbfc598bb0b01096cb77a72117f220c9292a5202588f3145264376df85aaef0

d7cc9d8775e5c58c2879cf99a4ca05e5c9e763e4f24c54036f923fb2bd2e0e76

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-01024RLUA-2024-06584RLUA-2025-06353

Credits

ReversingLabs · finder

Detect & block this

O3 blocks financialtimes-classic-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