Which versions of simplipayng are malicious?

The following npm versions of simplipayng are flagged malicious: 1.0.8. Treat any of these as compromised.

How do I remediate simplipayng if I installed it?

simplipayng establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed simplipayng — how do I know if it already compromised me?

If simplipayng 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.

Is simplipayng part of a known attack campaign?

Yes — simplipayng is associated with the IN-MAL-2026-014708, GHSA-qw5j-q6g9-pqhf 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 simplipayng across my projects, lockfiles, and CI pipelines?

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

Malicious package

simplipayngnpm

simplipayng is a confirmed malicious npm package (MAL-2026-12437) that opens a backdoor for remote access (malicious version 1.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simplipayng (npm)

MAL-2026-12437

Immediate action

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

npm uninstall simplipayng

What this malware does

dist/cjs/index.js appends an eval(atob(...)) blob to what appears to be a React Button re-export. The decoded payload queries public Ethereum RPCs for the latest transaction from the hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, extracts two IPv4 addresses encoded in the tx.to field, then fetches XOR-encoded next-stage JavaScript from those IPs over HTTP/HTTPS at the paths /0x/cls and /0x/ls and executes it via eval and spawn('node', ['-e',...], {detached:true}). Network and process sinks are hidden behind base64 wrapping and per-character \uXXXX unicode escapes for require('http'), require('https'), require('child_process'), and 'spawn'. Any project that require()s this package receives arbitrary remote code execution controlled by whoever writes to the on-chain dead-drop address, in a detached Node subprocess.

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

1.0.8

Indicators of compromise (SHA-256)

1cf21e1f6c1fc8a9e9caa3a8383da1b2fb4dd863fc531e17771209b14284e087

b4462e97d828e2448139b0e3f348c00cd4f9f5611b7886c6c199796f5895a5a8

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for simplipayng (version 1.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging simplipayng across your stack and pipelines.
If you installed it — respond
simplipayng establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If simplipayng 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.
How O3 protects you
O3 blocks simplipayng 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. simplipayng on npm has been identified as a malicious package (version 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014708GHSA-qw5j-q6g9-pqhf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks simplipayng-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database