NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

tick-forgenpm

Advisory published Updated

tick-forge is a confirmed malicious npm package (MAL-2026-13385) that executes malicious code on install (malicious version 11.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tick-forge (npm)

MAL-2026-13385
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tick-forge

What this malware does

The package's default export getPlugin fetches JSON from a hardcoded bare-IP endpoint (http://31.97.137.157:45000/icons/107) and passes the returned data.credits string to new Function(...) invoked with require, module, process, Buffer, Promise, and other Node globals injected. Any consumer calling the default export executes attacker-controlled code inside their Node process with full runtime capabilities. The loader is disguised with icon/CDN naming (IconProvider, iconDomain, a font-awesome-style path, a bearrtoken: "logo" header) while the actual network destination is a bare IP over plain HTTP and the response body is compiled as JavaScript.

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.

Malicious versions

1 flagged
11.5.2

Indicators of compromise (SHA-256)

1daa60c05b8646af76068f4319e2bcc94eae33db99bc94f4d1805b56b02af15b
ea28965c8e98731dba705fb8041ace7efa74984f5a78da68a450c07ef810c6af

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for tick-forge (version 11.5.2).

  2. If you installed it — respond

    Remove tick-forge 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.

  3. Did it already run?

    If tick-forge 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. tick-forge on npm has been identified as a malicious package (version 11.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rjvw-v893-2f7gIN-MAL-2026-016040

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tick-forge-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.

Explore

tick-forge (npm) malicious package — MAL-2026-13385 | O3 Security