Which versions of @zentrafinance/types are malicious?

The following npm versions of @zentrafinance/types are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate @zentrafinance/types if I installed it?

Remove @zentrafinance/types 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 @zentrafinance/types — how do I know if it already compromised me?

If @zentrafinance/types 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 @zentrafinance/types part of a known attack campaign?

Yes — @zentrafinance/types is associated with the GHSA-f5rj-fcq3-x58f 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 @zentrafinance/types across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @zentrafinance/types (version 1.0.2).

Malicious package

@zentrafinance/typesnpm

Advisory published May 16, 2026Updated May 19, 2026

@zentrafinance/types is a confirmed malicious npm package (MAL-2026-3815) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zentrafinance/types (npm)

MAL-2026-3815

Immediate action

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

npm uninstall @zentrafinance/types

What this malware does

The package @zentrafinance/types was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified '@zentrafinance/types' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

63e91c8566bb636e149ae8f06a3cf5c9fc9a2228588079b715ec280fb5c7bbd0

b036b0b8f11fb0cb0371d316b38abf1c2d968024094515fcbf88036fba92c0b3

1aa8866d3eaa828e8b575d8351ed3430237e14f71bb1af0acc90c468a7e8b8cb

Detection & response playbook

Malicious package

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

Campaign

GHSA-f5rj-fcq3-x58f

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @zentrafinance/types-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