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

mintel-taskbarnpm

mintel-taskbar is a confirmed malicious npm package (MAL-2026-15514) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mintel-taskbar (npm)

MAL-2026-15514
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mintel-taskbar

What this malware does

package.json line 11 declares the package's own name 'mintel-taskbar' as a dependency whose source is the bare HTTPS URL https://repo.securityctrl.com/mintel-taskbar, not a registry version range. On npm install, npm resolves this dependency by fetching whatever tarball that URL returns and installs it — running any lifecycle scripts inside the fetched tarball — with no version pin and no integrity check. Whoever controls repo.securityctrl.com therefore controls code executed on every installer's machine. The self-referential shape (dependency key equals the package's own name) combined with an implausibly high version (45.0.0) is consistent with a dependency-confusion lure that resolves against an internal package of the same name.

Malicious versions

1 flagged
45.0.0

Indicators of compromise (SHA-256)

5ebda78171ac8816c0e350f84923af0bad54c075f91cfcc1a7bcc26d36674c4f

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 mintel-taskbar (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mintel-taskbar across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-019076

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks mintel-taskbar-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

mintel-taskbar (npm) malicious package — MAL-2026-15514 | O3 Security