Which versions of is-number-object are malicious?

The following PyPI versions of is-number-object are flagged malicious: 1.0.8. Treat any of these as compromised.

How do I remediate is-number-object if I installed it?

is-number-object is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed is-number-object — how do I know if it already compromised me?

If is-number-object 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 is-number-object part of a known attack campaign?

Yes — is-number-object is associated with the RLMA-2025-03619, GENERIC-standard-pypi-install-pentest, RLUA-2026-00432 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 is-number-object 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 is-number-object (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 is-number-object across your stack and pipelines.

Malicious package

is-number-objectPyPI

Malicious code in is-number-object (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6526

Immediate action

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

pip uninstall is-number-object

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.8

Indicators of compromise (SHA-256)

c0658c6b882b62dbc0951bb4e3b29c2108210a21b29ee38ffd59db424e1f6dc5

3c02be6e910db26635ec0b017be94b6c09973e53e8b31848aa62bd6718b1f047

60c891b7eb9d0f5a8ca04cb59f7b91bac36fbcc7df40fcf44b9a46f8c969daf3

c0301fe2cd588be3a2840800b503be975c9bcf64cf26ddc65d4b26ef81a1e90d

f28696718b3ca41a2e870fa4824b1f03e693e57fc77838dd633cdd49ecd95688

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for is-number-object (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 is-number-object across your stack and pipelines.
If you installed it — respond
is-number-object is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If is-number-object 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 is-number-object 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. is-number-object on PyPI 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

RLMA-2025-03619GENERIC-standard-pypi-install-pentestRLUA-2026-00432

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks is-number-object-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring