Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

eslint-plugin-unicorn-ts-2npm

eslint-plugin-unicorn-ts-2 is a confirmed malicious npm package (MAL-2024-1019) that executes malicious code on install (malicious version 1.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-plugin-unicorn-ts-2 (npm)

MAL-2024-1019
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall eslint-plugin-unicorn-ts-2

What this malware does

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 'eslint-plugin-unicorn-ts-2' @ 1.1.6 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
1.1.6

Indicators of compromise (SHA-256)

600a19c9c91f8a7b2c7dd223a62020edbf79525791b8e36b3b67c0863d2b4557
b71b5afde24f585fa4738155252aed586c08f3603e822cf5a6ce4b67e2df87fd

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-plugin-unicorn-ts-2 (version 1.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-unicorn-ts-2 across your stack and pipelines.

  2. If you installed it — respond

    Remove eslint-plugin-unicorn-ts-2 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 eslint-plugin-unicorn-ts-2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks eslint-plugin-unicorn-ts-2 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. eslint-plugin-unicorn-ts-2 on npm has been identified as a malicious package (version 1.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rm77-vqrw-469p

References

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks eslint-plugin-unicorn-ts-2-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

eslint-plugin-unicorn-ts-2 (npm) malicious package — MAL-2024-1019 | O3 Security