Which versions of fetch-data-api-syncapi are malicious?

The following PyPI versions of fetch-data-api-syncapi are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate fetch-data-api-syncapi if I installed it?

fetch-data-api-syncapi 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 fetch-data-api-syncapi — how do I know if it already compromised me?

If fetch-data-api-syncapi 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 fetch-data-api-syncapi part of a known attack campaign?

Yes — fetch-data-api-syncapi is associated with the 2026-04-fetch-data-api-syncapi 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 fetch-data-api-syncapi 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 fetch-data-api-syncapi (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fetch-data-api-syncapi across your stack and pipelines.

Malicious package

fetch-data-api-syncapiPyPI

Malicious code in fetch-data-api-syncapi (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3100

Immediate action

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

pip uninstall fetch-data-api-syncapi

What this malware does

The package contains code to download and start a malicious executable. It's masqueraded using name similar to Windows services. In analyzed versions, the code was not automatically started, suggesting it's just a part of a campaign. Based on the dynamic analysis, the executable is likely an infostealer.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-04-fetch-data-api-syncapi

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

34f49fb4dcc6dd862bda7af4b571916ff47fd4c857158104c8d0a7e5d0af379d

dda63ba0d0dbd4ddf1d89523cacf89d51ffc9a25891e38cb49a9e424721fba9d

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 fetch-data-api-syncapi (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fetch-data-api-syncapi across your stack and pipelines.
If you installed it — respond
fetch-data-api-syncapi 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 fetch-data-api-syncapi 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 fetch-data-api-syncapi 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. fetch-data-api-syncapi on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-fetch-data-api-syncapi

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks fetch-data-api-syncapi-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