What does the tripica-library malware do?

The package tripica-library was found to contain malicious code. The OpenSSF Package Analysis project identified 'tripica-library' @ 999.1.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of tripica-library are malicious?

The following npm versions of tripica-library are flagged malicious: 999.1.0. Treat any of these as compromised.

How do I remediate tripica-library if I installed it?

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

If tripica-library 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.

How do I find tripica-library across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tripica-library (version 999.1.0).

Malicious package

tripica-librarynpm

Advisory published Jan 26, 2026Updated Feb 2, 2026

tripica-library is a confirmed malicious npm package (MAL-2026-507) that executes malicious code on install (malicious version 999.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tripica-library (npm)

MAL-2026-507

Immediate action

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

npm uninstall tripica-library

What this malware does

The package tripica-library was found to contain malicious code.

The OpenSSF Package Analysis project identified 'tripica-library' @ 999.1.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

999.1.0

Indicators of compromise (SHA-256)

4aad2e8ed1a98fda3be6ae6f8dd9efcdf30b15c58728a881bb5930a00bf05733

2094e4c510f7d9f01acaf3dcdb4e2fda46afbe56f235d8168d81bcb984e52fc3

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks tripica-library-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