job-posting-intent
Audited by Socket on Sep 20, 2026
4 alerts found:
Anomalyx3SecuritySUSPICIOUS. The stated purpose mostly matches the capabilities, but the skill depends on a third-party Apify Actor and an underspecified Rube/Composio export path, while the actual scripts are missing so token handling and network destinations cannot be verified. This is not confirmed malware, but the trust chain and credential forwarding are insufficiently transparent for a benign classification.
The code is intended as a job-search and lead-qualification utility with optional JSON and Google Sheets export. It does not show clear malware behavior such as reverse shells, system-data theft, persistence, or destructive actions. However, it contains a hardcoded JWT-like Rube MCP credential, which is an important supply-chain and credential-exposure issue; the token should be considered compromised and removed or rotated. The program also sends collected job/company data to external services and permits unrestricted caller-selected output paths. The supplied fragment is syntactically incomplete, so runtime behavior of the missing or malformed portion cannot be fully verified.
The code is not clearly malware, but it contains a significant supply-chain and credential-management risk: a bearer JWT is hardcoded and local job data is transmitted to an external MCP service for remote execution and Google Sheets upload. The token should be revoked or rotated, replaced with secure runtime authentication, and the external service and permissions should be independently verified. No clear obfuscated or destructive malicious payload is present.
The code appears to implement a legitimate integration that transfers local job-posting data to Google Sheets through Rube. No clear malware behavior or intentional sabotage is present. The hardcoded bearer token is a significant credential-management issue, and arbitrary input rows are transmitted to an external service without strong validation. Review the token, confirm the Rube destination is trusted, and consider formula-injection protections for untrusted spreadsheet values.