Malicious code in @activepieces/piece-google-forms (npm)
The npm package @activepieces/piece-google-forms versions 0.5.5, 0.5.6, and 0.5.7 contains malicious code. The package includes a source file that executes OS commands via child_process and sends hardcoded HTTP POST requests to an external destination. This behavior is inconsistent with legitimate Google Forms API integration and suggests a command-execution and data-exfiltration payload. The package name closely mimics the legitimate @activepieces ecosystem, indicating a possible supply chain compromise or malicious impersonation.
AI Analysis
Technical Summary
The published tarball for @activepieces/piece-google-forms versions 0.5.5 through 0.5.7 includes src/index.js that imports the Node.js child_process module to execute ping-style OS commands and issues hardcoded HTTP POST requests to a fixed external endpoint. This combination of command execution and network communication within a piece module loaded by the Activepieces host is indicative of an installer-side malicious payload designed for command execution and data exfiltration. Legitimate Google Forms integration would use the Google Forms REST API via HTTP helpers, not shell commands or hardcoded network calls. The package's naming similarity to the official @activepieces pieces increases the risk of supply chain attack or malicious package impersonation.
Potential Impact
Systems that install or run these specific versions of @activepieces/piece-google-forms may execute arbitrary OS commands and transmit data to an attacker-controlled server, potentially leading to unauthorized command execution and data leakage. This compromises the integrity and confidentiality of the affected environment.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Users should immediately avoid using versions 0.5.5, 0.5.6, and 0.5.7 of @activepieces/piece-google-forms. Verify package integrity and source before installation, and consider removing these versions if already installed. Monitor for updates or advisories from the package maintainers or npm regarding this issue. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Malicious code in @activepieces/piece-google-forms (npm)
Description
The npm package @activepieces/piece-google-forms versions 0.5.5, 0.5.6, and 0.5.7 contains malicious code. The package includes a source file that executes OS commands via child_process and sends hardcoded HTTP POST requests to an external destination. This behavior is inconsistent with legitimate Google Forms API integration and suggests a command-execution and data-exfiltration payload. The package name closely mimics the legitimate @activepieces ecosystem, indicating a possible supply chain compromise or malicious impersonation.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The published tarball for @activepieces/piece-google-forms versions 0.5.5 through 0.5.7 includes src/index.js that imports the Node.js child_process module to execute ping-style OS commands and issues hardcoded HTTP POST requests to a fixed external endpoint. This combination of command execution and network communication within a piece module loaded by the Activepieces host is indicative of an installer-side malicious payload designed for command execution and data exfiltration. Legitimate Google Forms integration would use the Google Forms REST API via HTTP helpers, not shell commands or hardcoded network calls. The package's naming similarity to the official @activepieces pieces increases the risk of supply chain attack or malicious package impersonation.
Potential Impact
Systems that install or run these specific versions of @activepieces/piece-google-forms may execute arbitrary OS commands and transmit data to an attacker-controlled server, potentially leading to unauthorized command execution and data leakage. This compromises the integrity and confidentiality of the affected environment.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Users should immediately avoid using versions 0.5.5, 0.5.6, and 0.5.7 of @activepieces/piece-google-forms. Verify package integrity and source before installation, and consider removing these versions if already installed. Monitor for updates or advisories from the package maintainers or npm regarding this issue. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13396
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cf8cbf8831d5391ae723
Added to database: 08/06/2026, 18:16:44 UTC
Last enriched: 08/06/2026, 18:33:11 UTC
Last updated: 08/06/2026, 18:33:11 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.